How to link work, invoice, and payment

The work was delivered two weeks ago, the invoice still hasn't been issued, and the client is sure you simply forgot. A solo professional rarely loses money on price — more often on pauses: between acceptance and invoice, between invoice and reminder.

In PRO-dela, an invoice is assembled from project line items and data, exported to PDF, and sent to the payer with a notification. Bank details and the stamp are set up once. Let's walk through the path from completed work to closed payment.

Why money gets lost in the pauses

Issuing an invoice is unattractive work: it begins after the pleasant "work accepted" and consists of manually transferring line items, bank details, and numbering. Every time from scratch — which is why it gets postponed.

The second pause comes after sending. The invoice is out, but tracking the status manually feels awkward: a "polite" reminder is hard, forgetting is expensive. Without a system, the pause drags on for weeks.

The third pause is between projects. The complexity of "which invoice is unpaid" grows quadratically when working with several clients: each has their own formats, statuses, and deadlines.

Step 1. Assemble the basis for the invoice

An invoice in PRO-dela is built from line items — work and amounts. At stage closure, the basis is at hand: the stage's tasks show what was done, acceptance shows what was accepted. The invoice can be assembled from project data and the line items adjusted to match what was agreed.

Check three things: completeness (did everything completed make it in), alignment with what was agreed (are there line items the client won't recognize), and the arithmetic. An invoice with an error in the total is a hit to trust that took months to build.

Write line item descriptions for the client's accounting department, not for yourself: "Homepage prototype, stage 2" is better than "per assignment".

Step 2. Issue the invoice as a document

Bank details, logo, stamp, and signature are set up in the company once and appear in every document. The invoice is exported to PDF — that is the document the client receives: with your bank details, line items, and total.

A notification goes to the payer — the invoice reaches the right person with context instead of getting lost in a shared "info@" inbox. If the payer isn't the person who accepts the work, specify them: this is a typical cause of delays.

The invoice date is also a tool: it starts the payment deadlines in the client's accounting. Issue it on the day of acceptance, not "when there's a minute" — the difference for your cash flow is usually a week.

Step 3. Drive it through to payment

The invoice status is changed manually: the platform doesn't accept online payments — it tracks the document and its state. An honest status is the basis for a conversation about overdue payment: "invoice No. 14 dated the 12th, status — unpaid" sounds well-founded.

Invoice events arrive in notifications — including Telegram: status changes and overdue payments are visible where the rest of the work is. Reminding the payer stops being a psychological problem when the status is right in front of you.

In the Friday wrap-up (covered in a separate article in the series), check invoices alongside tasks: work, time, and money are parts of one indivisible review.

Example: the "Prototype" stage is closed

A studio completes the "Prototype" stage for a logistics company's website. The invoice is assembled from the stage's line items, two prices are adjusted per what was agreed, and the total matches the proposal.

The PDF with bank details and stamp goes to the payer — the client's accountant, not the manager. Six days later the status changes to paid; in the project's Friday wrap-up it's clear: work accepted, invoice closed, document attached.

This is a training example. What matters is the order: basis from the project, document with bank details, notification to the payer, status — and no "I forgot to issue it".

How it works in PRO-dela

The platform has an invoices section: line items, statuses, PDF, payer notification, document linking. An invoice can be assembled from scratch or from a project; documents — acceptance certificates and appendices — are attached to the invoice.

There is no online payment acceptance in the platform: an invoice is a document with a status that the professional manages. Money arrives to your bank details directly, with no intermediaries and no acceptance fees.

What most often gets in the way

The first mistake is saving "the invoice for the end of the project" on long engagements: stage closed — invoice issued. The second is the same reminder text for every overdue payment: check the status and history, and conversations get shorter.

The third is not attaching documents to the invoice: in a dispute, searching through correspondence costs more than one button.

Frequently asked questions

Can payments be accepted right in the platform?

No, there is no online payment acceptance. The platform tracks the document, statuses, and notifications; money goes to your bank details.

Are the stamp and signature mandatory?

As your working context requires. They are set up in the company and used in documents; for work without a stamp, the field simply stays empty.

What does the payer see?

A notification with the invoice and the PDF document. They have no access to your workspace.

Issue an invoice for a closed stage

Find a closed stage for which an invoice hasn't been issued yet, assemble the invoice from its line items, and send the payer a notification. One closed document will remind you what cash flow looks like without pauses.

Sign up for PRO-dela. Current terms of use are available on the pricing page.