The coding rules live in the system, not in your head.
Every client's AP runs the same way: invoices coded on arrival to their GL, cost centres, projects and entities, checked before their payment run, posted to their ledger.
One system, one login per client.
Each client runs their own Quid, set up with their own chart of accounts, cost centres, rules and approval chain. The coding logic sits in the system rather than in your notes, so picking a client back up after two weeks does not start with remembering how they code things.
Coding learned from their own history
Quid reads how that client has posted before and codes new invoices the same way. GL, cost centre, tax, project and entity, per line. A new client does not start from a blank rulebook.
Their rules, their approval chain
Thresholds, approvers, out of office cover and vendor-specific handling are set per client. What you decided in March is still being applied in September, whoever is on the invoice.
Their ledger, untouched
Coded lines post to whatever that client runs: DATEV, their ERP, another accounting platform, or through the REST API. You are not standardising five clients onto one system to make this work.
From signed contract to running, in 2 to 4 weeks.
Their AP inbox, Drive, Slack, supplier portals or ERP on one side, their accounting platform on the other.
Quid reads their posting history and proposes the coding patterns it finds. You correct what is wrong.
Approval chains, confidence threshold, vendor and cost centre rules, agreed once with the client.
Invoices arrive coded and checked. Exceptions come to whoever you nominate.
The setup work happens once per client, not every month.
You approve payments for clients you work with a few days a month. Every held line shows the rule it broke, the document behind it and who approved it.
Separation between clients
Each client’s data sits in its own workspace, with access granted per client. Nothing crosses between engagements.
Proprietary AI confidence score on every line
With a threshold you set per client. Below it, the line comes to a person rather than posting.
Reason stored per decision
Every coding and hold decision keeps its reason and its source document, so a question six months later has an answer.
Full audit trail
Receipt to posting, including who approved what and when. Their auditor gets evidence rather than recollection.
Controls before the payment run
Duplicates, price variances against contract and supplier history, and bank detail changes, all held before money moves.
Their ERP stays the source of truth
Quid posts into it. You are not asking a client to replace a system to work with you.
The constraint is your hours, not their volume.
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.
Month-ends arrive together. The work that used to fill that week is already done when it starts.
Who holds what.
The client holds the contract
Quid is billed to the client, in their name, on their account. If your engagement ends, their system and their history stay with them.
You get access, not ownership
You are added to their workspace with the access level they agree to. Access can be removed by them at any time.
Partner conversation
We have a partner programme. Get in touch and we will walk you through it.
Questions
Can I work across several clients from one account?
Each client has their own workspace and you are added to each. There is no single cross-client view today.
How is one client’s data kept separate from another’s?
Each client is its own workspace with its own access list. Access is granted per client and per person, and nothing is shared between them. Hosting is in the EU with data residency options, and no client data is used to train models.
What happens when an engagement ends?
The client keeps their workspace, their coding history and their documents. Your access is removed by them. Nothing of theirs leaves with you, and nothing of theirs is lost.
Which accounting systems do you support?
Coded lines post to DATEV, ERPs and other accounting platforms, or through the REST API.
Who pays, the client or me?
The client, on their own account.
How long does a new client take to set up?
2 to 4 weeks from connecting the sources to running on live invoices.
What if a client’s coding is inconsistent today?
Quid learns from what is there and sends anything below the confidence threshold to a person. The first weeks are where the patterns get set, and your corrections become the default from then on.
One way of working, across every client.
A 30 minute call on how Quid would fit your clients' systems and your own week.
Book a demo