TALLYLANE / HOW THE API WORKS
Your system. One invoice-to-cash flow.
Create customers and invoice drafts from your system. Use Tallylane to review the invoice, confirm payment and track its accounting outcome.
From customer to accounting record
- Create a customer
Save who you bill and their billing details.
API or workspace - Save a draft
Tallylane calculates the totals from the current tax details.
API or workspace - Review and issue
An authorised person approves the invoice, then issues it.
Human review - Confirm payment
A signed Stripe event is checked against provider records before the balance changes.
Stripe Sandbox - Verify in Xero
Transfer the invoice and confirmed payment to the connected UK demo, then verify both.
Xero UK demo
Payment and accounting have separate statuses. Automatic Xero transfer after payment is in development.
One account. Your assigned business.
From your backend
A scoped account API credential lets your system create customers, save drafts and read current records.
In the workspace
Your user signs in to review and issue invoices. Approval follows the business’s configured review policy.
Your administrator provisions access. Credentials stay on your server; each request checks current permissions for the assigned business.
Know what each result means
- Draft
- Saved work, ready for review. Saving does not issue an invoice, send it or charge the customer.
- Unresolved totals
- Unknown or unsupported tax context leaves VAT and gross null, never zero. Resolve the missing details before approval.
- Paid
- A confirmed payment has been allocated to the invoice. A checkout link or redirect is not payment confirmation.
- Verified in Xero
- The invoice and mapped payments have been independently checked in Xero. A connected account alone does not establish this.
- Unknown outcome
- Keep the original command ID and recover its result before trying again. A new command can duplicate the action.
Explore the API contract
Swagger shows the backend’s routes, request bodies, responses and authentication requirements. The OpenAPI file is the same machine-readable contract for your tooling.
The specification describes implemented routes. Customer integration instructions and enabled capabilities will be provided with your account.