Clear requests
Give the customer a clear amount, reason, and due date so there is no ambiguity about what they owe.
Revenue / Invoicing
An invoice is a conversation about getting paid. Connect the request, the customer, and the payment outcome in one workflow.
SAMPLE INVOICE
ETB 1,000.00
Business services / INV-001
Pay invoice
The invoice workflow
An invoice is more than a document. Zapi keeps the request, the customer, and the payment outcome connected from send to settle.
Give the customer a clear amount, reason, and due date so there is no ambiguity about what they owe.
Send the invoice through the channel that fits the customer, with a payment path attached from the start.
Payment collection is tied to the original invoice, so the outcome always relates back to the request.
See whether an invoice is requested, paid, or overdue without chasing it across separate tools.
Unpaid invoices prompt the customer automatically, recovering revenue without a person following up each time.
Your operations team sees invoice activity alongside other payment flows in one shared picture.
Collection, connected
Each stage of an invoice is a decision your team and your customer make together. Keep them connected so nothing falls through.
01 / INVOICE LIFECYCLE
Give the customer a clear amount and reason to pay, with a payment path attached.
02 / INVOICE LIFECYCLE
Connect payment collection to the original invoice so the outcome is never orphaned.
03 / INVOICE LIFECYCLE
Help your team relate the payment outcome to the customer account and the work it represents.
Built for one-off billing
From a single project to an ad-hoc charge, the same invoice workflow adapts to how your business actually bills.
Bill a client for a completed engagement with a clear amount and due date.
Send a single invoice for project work and track payment without a recurring setup.
Invoice at each milestone and keep the project total connected to what has been paid.
Reconcile an outstanding balance with an invoice that ties back to the customer.
Good to know
What teams ask before they put one-off billing on Zapi.
Every invoice carries its own payment path. When the customer pays, the outcome is tied back to the original request, so your team never has to match a payment to an invoice by hand.
Yes. Each invoice has a clear status — requested, paid, or overdue — visible alongside your other payment activity, so nothing slips through without a follow-up.
Yes. One-off invoices and recurring charges live in the same records, connected to the same customer profile, so your team sees the full billing picture in one place.
Unpaid invoices prompt the customer automatically on a sensible schedule, recovering revenue without a person chasing each one. You stay informed about which invoices need attention.
Related products
Turn a one-off invoice into a recurring billing relationship.
The payment API that collects every invoice.
Keep invoices, history, and context on one customer profile.
Plan the tax treatment that belongs on each invoice.
Track invoice status alongside payment activity.
Collect the payment an invoice requests.
Start building with Zapi
One integration for payments, payouts, and virtual accounts. Start in test mode and grow from there.