Illustrative scenario: The work was delivered in week five. The invoice went out in week six. By week nine, the money still has not moved, and the designer is following up with a client she otherwise delighted.
Why approved work can still wait for payment
The commercial system defines what the client is buying: discovery, scope, proposal, approval, and agreement. The delivery system records how the work is completed: checkpoints, revisions, and acceptance. Ruul supports the transaction stage through its Agent of Record service, invoicing, payment collection, and payout. The client and creative professional still define the scope, approve the work, and agree on the commercial terms. Ruul Support: How invoicing works
Three handoffs that determine whether the work gets paid
Agreement
- Clarify: buyer, scope, price, acceptance criteria, and finance requirements.
- Keep: discovery notes, scope, proposal, procurement details, and signed terms.
- Transaction support: Ruul can act as the transaction counterparty; the client and creative professional negotiate their service agreement.
Delivery to payment
- Clarify: how both sides know the agreed work is complete and finance can process the invoice.
- Keep: versions, change orders, approvals, acceptance, invoice, and payment status.
- Transaction support: Ruul handles eligible invoices, collection, compliant invoicing, and payout.
Close or continue
- Clarify: whether the need ends, recurs, or calls for a separately scoped project.
- Keep: closure or renewal decision, updated scope, and transaction and delivery records.
- Transaction support: scheduled invoices and card subscriptions are different options; choose the one that matches the work and current terms.
Discovery, audits, and workshops can themselves be paid engagements. Agree on the work and payment terms before delivery creates an obligation to collect.
Qualify the buyer before the brief becomes a commitment
Discovery should cover more than the creative brief. Ask what the buyer’s finance team needs to approve the supplier and process payment. Requirements may include a purchase order, vendor registration, tax or company information, a specific payment method, a budget owner, or an approval sequence. Map the requirements that apply before delivery is complete.
Scope is the load-bearing document. Define deliverable counts and formats, revision rounds, exclusions, timing, the change process, and acceptance criteria. A milestone is useful when both sides can tell whether it has been reached. “Client approves concepts” is vague. “Selected direction delivered with agreed applications, in-scope revisions incorporated, and written approval recorded” gives the client and creative team a shared completion test.
The proposal turns the scope into a commercial commitment. Choose the pricing structure and payment schedule before work begins. A fixed-fee project can still be invoiced against completed milestones; pricing and invoice timing are separate choices. Confirm procurement readiness as part of approval. If accounts payable requires a PO number or other reference on the formal invoice, verify that Ruul’s current invoice fields include it. Extra Notes are visible in invoice details and checkout, but Ruul says they do not appear on the invoice PDF. Ruul Support: How to create an invoice
The agreement records what the parties have accepted. For transactions processed through Ruul, Ruul acts as the Agent of Record and legal counterparty and handles the invoicing and compliance steps described in its current terms. The service agreement and creative scope remain the parties’ responsibility. Ruul Support: What Is an Agent of Record?
Make completed work payable
The delivery system should create its own evidence trail: kickoff decisions, versions, feedback, change requests, and completion records. Keep approvals in a form both sides can retrieve. If the commercial model requires a deposit before work begins, confirm the current Ruul workflow with its support team before writing that payment schedule into the process. Ruul’s current invoicing guide describes creating an invoice after a project or task has been completed.
Milestones are part of the engagement. Define them in the scope, document acceptance, and decide whether each completed checkpoint should trigger a separate invoice. The invoice should match the approved work and payment terms.
When the client accepts a completed, in-scope checkpoint, record the approval and prepare the invoice. Work beyond the agreement calls for an approved change order with its own scope and price. If completion is disputed, resolve the disagreement against the agreed deliverables before treating it as a collection issue.
A completed milestone should have evidence of completion before it becomes a payment event.
Ruul’s current flow is: finish the project or task, create an invoice with the amount, currency, and service description, and send the secure payment link to the client. After the client pays, Ruul issues its own compliant commercial invoice and releases the payout after standard checks. Ruul Support: How invoicing works
The current guide lists a standard invoice range of €100 to €100,000 or equivalent per invoice and limits invoices to eligible digital services. Descriptions must be in English, except for invoices to companies registered in Türkiye, which must be in Turkish. The description must not include the professional’s or company’s name, a date, or amount calculations. Check the accepted service category and transaction requirements before creating an invoice, since platform rules can change. Ruul Support: Accepted Service Categories and Limitations
For an unpaid invoice, Ruul’s Payment Chaser can send up to three reminder emails. The first is scheduled five business days after creation; when the invoice is already older, the first reminder may be sent that day. Later reminders are scheduled every three business days. A client dispute or blocked finance process still needs a direct conversation. Ruul Support: Payment Chaser
Match the payment route to the engagement
Clients can pay an invoice through its secure link by card or bank transfer, without creating a Ruul account. For a bank transfer, the client should use the reference shown with the payment instructions; the reference helps Ruul match the transfer to the invoice. The available option can depend on the transaction and invoice details, so confirm it with the client before delivery when finance requirements are strict. Ruul Support: Why did I get an invoice from Ruul?
A scheduled invoice and a subscription describe different billing arrangements. A scheduled invoice is generated each month and the customer pays each invoice manually. A subscription is approved once and charged automatically to the customer’s saved card each period. Match the setup to the scope and confirm the current billing terms with both sides. Ruul Support: How to create an invoice
Track payment, payout, and records
Ruul’s dashboard shows invoice statuses. After Ruul receives the client’s payment, payout preparation usually begins within one business day. Receiving banks can take additional time; the current help page says international SWIFT transfers may take three to four business days, depending on intermediary banks. A first-time business verification can add time before funds reach the freelancer. Ruul Support: How to manage your invoices
Maintain two connected records: the invoice and payment timeline, plus the creative record of scope, versions, approvals, and acceptance. Ruul says invoices are financial records that cannot be deleted; an obsolete invoice can be archived and found through the status filter. Keep the delivery evidence in the practice’s own archive.
Where payment gets delayed
Procurement appears late. The scope may be accepted while finance still needs a PO number, vendor record, or invoice field. Ask what the buyer needs before approval.
Completion is open to interpretation. “A set of social templates” leaves count and acceptance unclear. Put those terms in the scope so review does not become a dispute about what was purchased.
No one owns the payment trigger. Work is approved, but nobody creates the invoice or confirms the buyer received it. Name the owner and tie the invoice to recorded acceptance; the buyer’s payment cycle begins when finance receives the transaction.
Follow-up and renewal lack a decision owner. Schedule routine reminders where appropriate, and contact the client directly about disputed work. Start a renewal conversation when a recurring need is visible and scope the next engagement before pricing it.
After delivery, choose whether to close or continue
The completed project gives both sides evidence about delivery, support needs, and whether the work is likely to recur. For a one-off need, close the engagement cleanly or scope a separate project when another need appears. For recurring work, agree what will repeat and check that the chosen Ruul billing method fits. Revisit scope and price for every new engagement.
A short handoff check
Before kickoff, confirm three owners:
- Who approves scope and procurement?
- Who records acceptance?
- Who sends and follows the invoice?
Keep the delivery archive alongside the transaction record and reconcile them at each completed milestone.
In the opening scenario, the work was ready in week five but the invoice went out in week six. That gap sits before the client’s payment cycle begins. Giving someone clear ownership of the acceptance-to-invoice handoff can prevent avoidable waiting.
