Invoices arrive coded and checked.
Every line gets its GL account, cost centre, project and entity on arrival. Duplicates, price changes and new bank details are caught before the payment run. You review what needs a decision and approve.
The exceptions inbox
Everything that passed the checks is coded and posted. What reaches you is the short list, each item with the reason it stopped and the line it stopped on. You correct it once and the correction becomes the pattern.
Coding on arrival
GL, cost centre, tax, project and entity assigned per line, based on how you have posted before. A single invoice can carry lines for three cost centres and two entities, and each line gets coded on its own.
Checks before you pay
Duplicates across entities, locations and sources. Price variances against contract and supplier history. Bank detail changes flagged and held before payment. Early payment discount windows surfaced with what taking them is worth.
Less work at month end
Quid reads the service period from each invoice and sets up the prepaid schedule. You approve it instead of building it. Fewer open items, fewer manual entries.
Every decision is visible, and every decision is yours.
You set the rules
Coding rules per company and per vendor. Quid applies them, it does not invent them.
You set the threshold
Anything below your confidence level comes to you rather than posting.
You can override any line
Your correction is stored and becomes next month’s default.
Every decision has a reason
Stored with the source document, visible on the line.
Out of office cover
Approval routing has cover built in, so nothing sits waiting for one person.
The judgment stays with you
Quid handles the repeat work. Supplier queries and the calls that need a person are still yours.
The result
Invoice volume handled by the same two person team.
Posted automatically. The rest arrive as exceptions with a reason attached.
From first connection to running on live invoices.
Share of finance team time spent on AP, before and after.
Questions
Does this replace my job?
It removes the repeating part: classifying, coding, chasing and re-keying. Review, exceptions, supplier relationships and the decisions that need judgment stay with you. The teams we work with handled more volume rather than fewer people.
What happens when it codes a line wrong?
Lines below your threshold never post, they come to you. For anything that did post, the reason and the source document are on the line, and a correction updates the pattern.
Does it send a proper posting batch to DATEV?
Coded lines post to DATEV and other accounting platforms, with the document attached.
Can I keep doing the payment run the way we do now?
Yes. Quid runs the checks before it and flags what should not go out. The run itself stays your process.
How are early payment discount deadlines handled?
Payment terms are read when the invoice arrives. You see the window, the status of approval and what taking the discount is worth.
What about XRechnung and ZUGFeRD?
Both are ingested natively, along with Peppol, and kept in their original structured format.
See the e-invoicing page →How long until it is running?
2 to 4 weeks.
An inbox that only shows what needs you.
A 30 minute call on how Quid fits your entity structure and existing stack.
Book a demo