Document approval for finance teams
Change an approval rule yourself. Without a statement of work.
Invoices, purchase orders, contracts and expenses through one approval chain, with one audit trail. Configured by the controller who owns the process — not by a consultant, six weeks from now.
- Five document types
- One chain
- Invoices, POs, contracts, expenses and travel route through the same engine.
- Every decision
- Signed
- Bound to the document's full contents, in an append-only log.
- Approve from
- The email
- No login, no app, no chasing. It works from a phone on a Sunday.
The daily loop
Four steps, and you configure every one of them.
Nothing here is bespoke work. Each step is a setting in the product, editable by whoever owns the process.
1It arrives
Drop in a PDF or file it by hand. Vendor, amount, dates and line items are read out of the document, and duplicates are caught before anyone looks at them.
2It routes
The chain you configured decides who sees it, in what order, and by when — on your working calendar, not on calendar days.
3Someone decides
From the web, or straight from the email. Out of office redirects to a delegate; overdue escalates up a ladder you set.
4It is on the record
Who, what, when, and what the document said at that moment — in a hash-chained log the database itself will not let anyone edit.
Why we exist
The rule you need to change is a form, not a ticket.
Approval software is usually sold with an implementation partner attached, because the routing lives in configuration only they understand. Then finance changes a threshold and waits three weeks.
Approval chains are edited in the product
Steps, who approves, whether everyone or any one of them, the SLA in working hours, and the condition that decides whether a step runs at all.
Publishing is versioned, not destructive
A published chain is frozen. Editing it drafts the next version; publishing that retires the last one. Anything already in flight keeps the plan it started under, so changing a rule never rewrites a document's history.
Spending rules are written in plain expressions
amountBase > 5000 && payload.poNumber == null— validated when you save, so a typo cannot silently switch a control off.
Invoices over $10,000
Applies to invoices · published
- 124h
Manager sign-off
The submitter's manager
- 216h
Finance review
Anyone with Finance
- 348h
Over $10,000
A named person · CFO
Overdue → manager +8h → Finance +16h → hold for a human
Controls
The checks finance is actually buying.
Routing is table stakes. These are the reasons a controller signs off on a purchase.
Duplicate invoices
The same invoice, filed twice, under a slightly different reference. Caught on vendor, amount and date rather than on an exact string match.
Vendor bank changes
Flagged when a vendor's account details differ from the last invoice you paid — the single most expensive thing to miss.
Threshold splitting
Two invoices just under the limit that needs a second approver, from one vendor, in one week.
PO and receipt matching
Ordered, received, invoiced — reconciled, with the mismatch named rather than a red cross.
Self-approval
Blocked, and recorded as blocked. Configurable per workspace, because sometimes the owner really is the only approver.
SLA on working hours
An invoice that lands at 5pm on Friday is not overdue on Sunday. Holidays are yours to define.
# the database refuses, not the app
UPDATE audit_events SET action = 'tampered';
ERROR: audit_events is append-only:
UPDATE on seq 1 was refused.
# and anyone can check the chain
GET /api/admin/audit/verify
{ ok: true, checked: 4182, problems: [] }
Evidence
An audit trail your auditor can verify without trusting us.
Every event carries a sequence number, the hash of the one before it, and a hash of itself. A gap, a fork or an edited row is arithmetic, not opinion.
Append-only, enforced in Postgres
A trigger refuses UPDATE and DELETE for every role, including the database owner. There is no application path that can rewrite history because there is no database path either.
Decisions are signed over the document
An approval is bound to the document's full contents at that moment. Change the amount afterwards and the signature no longer matches what was approved.
Verifiable on demand
One endpoint walks the chain and reports the exact sequence number of any divergence. Give it to your auditor.
Fits how you already work
The approver should not have to learn anything.
The person holding up your month-end close is busy. Meet them where they are.
Approve from the email
Both buttons open a confirmation page — nothing is decided until it is confirmed and signed there. Works from a phone without an account.
Single sign-on and 2FA
Microsoft Entra and Google, or email and password with TOTP and recovery codes. A workspace can require SSO and mean it.
Webhooks and a REST API
Signed, idempotent deliveries with retries and a replayable dead-letter queue. Tokens are issued and revoked by you, in the product.
Multi-workspace by design
Isolation is enforced by Postgres row-level security, not by a WHERE clause someone might forget.
Pricing
Priced per workspace, quoted on what you actually need.
No implementation fee, because there is no implementation. Tell us your volume and we will give you a number in the first conversation.
Starter
A finance team getting off email and spreadsheets.
Talk to us
Monthly or annual, no setup fee
- Up to 10 approvers
- All five document types
- Configurable approval chains
- Spending policies and AP controls
- Hash-chained audit trail
- Email approve and reject
Growth
Most chosenMultiple entities, or an auditor who asks specific questions.
Talk to us
Monthly or annual, no setup fee
- Unlimited approvers
- Microsoft Entra and Google SSO
- REST API, webhooks and API tokens
- Delegations and escalation ladders
- Business calendars per workspace
- Accounting export
Enterprise
Regulated, or answering to a group finance function.
Talk to us
Monthly or annual, no setup fee
- Everything in Growth
- Enforced single sign-on
- Audit trail export and verification
- Data processing agreement
- Priority support with an SLA
- Onboarding help if you want it
Questions
The ones we are actually asked.
- How long does it take to get running?
- You can have a workspace, a chain and your first approval the same day. There is no data migration to schedule and no configuration we do on your behalf — that is the entire product thesis.
- Do we have to move our accounting system?
- No. Nextpense is the approval layer in front of whatever you already use. Approved documents export for posting, and the API is there if you want to push them automatically.
- What happens to an approval that is already in flight when we change a rule?
- It finishes under the rules it started with. The chain a document travelled is frozen onto it when it is submitted, so editing a template never rewrites history — and an auditor can see which version governed which document.
- Can approvers act without an account?
- Yes, from the email. The link opens a confirmation page and the decision is signed there. They still appear in the audit trail as themselves.
- How is our data separated from other customers?
- By Postgres row-level security, with the application connecting as a role that cannot bypass it. A query that forgets to scope returns nothing rather than everything.
- Can we get our data out?
- Yes. Documents, decisions and the full audit trail, on request or through the API. It is your record of who approved what.
Bring us the rule you have been waiting three weeks to change.
Thirty minutes, screen shared, using your actual approval process. We will change that rule while you watch. If it takes longer than a minute, the pitch was wrong and you should not buy it.
- No slide deck
- No implementation quote at the end
- A working workspace you keep
Or write to us at sales@nextcoretechnology.com