# Billing and Invoicing: invoices, quotes and payments

Dokimore documentation · Plans, billing and your account · Updated 2026-11-16 · 8 min read

Written for: Engineering managers, People evaluating or buying tools, Product owners · Where it applies: every market

> Billing & Invoicing is the module a team uses to bill its own clients, on the Team plan and above. It issues invoices, quotes, credit notes and debit notes with tax computed on the server from your seller profile and each client's country; records payments your finance system received, pushed to it or pulled from an endpoint you expose, each applied exactly once; generates invoices from a spreadsheet, from contracts or from metered usage in a checkpointed billing run; and exports e-invoices as IRP JSON or Peppol UBL. Dokimore never takes a payment on your behalf.

## Set up who is selling

Tax Settings is read first. Who is selling: the legal or trading name, the street address, the authorised signatory and a logo (PNG or JPEG up to 300 KB). Tax registration: the seller country and state, the registration and the export scheme, which together decide the tax on every invoice. Document defaults: the currency, an invoice prefix of up to five characters, the default service code, an approval threshold above which a second person must approve an invoice before it is issued, rounding of the total, the month the fiscal year starts (it drives the invoice series), the terms printed on every invoice, and bank accounts (the default one prints on the PDF; an account named on an issued invoice is archived, never deleted). Several legal entities can share one workspace, each with its own registration, currency and invoice series.

Own tax rules per buyer country, for a rate your adviser has confirmed that the catalogue does not model, and withholding expectations (shown as a note, never subtracted) complete the profile. A change applies to invoices created after it; an issued document keeps the tax facts it was issued with. A style profile (page size, accent colour, font, logo width, watermark, labels in five languages) is frozen onto each document when it is issued, so a rebrand never changes an invoice already sent.

## Invoices, quotes and notes

An invoice names a client (legal name, address, tax id and contact details, which print on the invoice; the address and contact details are encrypted at rest), a purchase-order reference, the currency with an exchange rate and its source and date when it differs from the home currency, the due date and payment terms, and the lines: description, service code, unit, quantity, unit price, line discount, tax category and, with a written reason, a rate override. Additional charges are taxable unless unticked; deductions after tax cover an advance received, withholding the customer will apply, or a credit note. "Create draft & download PDF" makes the draft; a document moves through draft, pending, paid, overdue and cancelled. Supporting evidence is attached as annexures and listed on the invoice with a checksum (images can be appended as pages; a PDF annexure is listed and downloadable, never merged). A receipt prints on an 80 mm roll.

A quote is an offer, not a receivable: its own number series, a validity date instead of a due date, and it expires rather than going overdue. Converting an accepted quote re-prices it under the tax profile in force on the conversion date. A credit note or a debit note keeps the original's tax treatment and takes its own number; the credit is applied to the balance and the debit increases it.

## Payments, in either direction

Dokimore never takes a payment: your finance system does and stays the source of truth. The page keeps the two in step in whichever direction your estate supports: your system pushes a payment to the billing API with an integration key, or the platform pulls from an endpoint you expose (https and a public address only; the credential is stored encrypted and never shown again). Both carry the same idempotency key, so a payment that arrives twice, from a retrying queue or an overlapping poll, is applied exactly once. A payment in another currency books its exchange difference in the home currency, and the sync log shows what was applied, already known or rejected.

## Invoices without typing one

- Spreadsheet import: upload an .xlsx, .xls or .csv; the columns are worked out from the header names, or from what the values look like when the headers say nothing; rows are grouped into one document per client (or per invoice reference), so 600 rows become the dozen invoices they represent. Nothing is created until you press Generate, the first 5,000 rows are read, unknown clients are created from the sheet, and the file itself is never stored, only the cells read from it. Tax is still computed by the server; the sheet never sets a rate.
- Products and price plans (a flat fee per period, per unit, tiered, volume or stair-step, with included units and an overage price), contracts that bill a client a fixed set of products every cycle (pause, skip a cycle, end), and usage events your systems push with an event id so a retried batch never double-counts.
- The billing run: every client with a contract due in the period or unrated usage inside it, executed as a checkpointed job of 50 clients per chunk; a failure is retried three times then parked in a dead-letter list, and a crash resumes from the checkpoint without re-billing anyone. "What would bill" previews a run without billing. PDFs are pre-rendered as a separate batch, and a reconciliation check confirms that totals, payments, credits, balances and number series agree.

## E-invoicing

For India, the invoice exports as IRP JSON; the IRN and the signed QR the portal returns are recorded on the invoice and print on the PDF, and a cancellation within the 24-hour window goes through the same page (after that, a credit note). A built-in sandbox rehearses the round trip with a portal-shaped IRN and a signed QR that is not a legal IRN. For Peppol, the invoice exports as UBL (BIS 3.0) to send through your Access Point, by hand or through a gateway you configure; every transmission and connection test leaves a row in the transmission log.

## Audit, revenue and backup

Every billing action is written to the activity log with ids and codes, the caller's address hashed, and no request body or credential; every document is mirrored into typed tables for finance and reporting, and a check proves the mirror equals the document. Revenue recognition is straight-line by days across the service period of a line, with the unearned part shown as deferred; invoiced is not earned. A backup is a portable JSON of clients, documents, products, contracts and catalogue, without sealed credentials; a restore skips anything already present and never overwrites, because a statutory invoice number is never reissued. Integration keys for your ERP or order system come with an OpenAPI document and an idempotency header on invoice creation, so a network timeout can never produce a second invoice. The dashboard totals cover the most recent 5,000 invoices.

## Questions people ask about this

### Does Dokimore collect the money?

No. Your finance system receives payments and stays the source of truth; the module records them, pushed by your system or pulled from an endpoint you expose, each applied exactly once.

### Can I set my own tax rate?

Per buyer country, as an own tax rule your adviser has confirmed, and per invoice as an override with a written reason. Otherwise the server computes the tax from your registration and the client's country, and the sheet or the API never sets a rate.

### Is this where I see my Dokimore subscription?

No. Your own plan, its allowances and its orders are on your plan page. This module is for the invoices you send to your clients.

This guide is about the Team plan, which includes Billing & Invoicing: https://dokimore.com/pricing

Source: https://dokimore.com/documentation/billing-and-invoicing
