Accounts payable
The invoice is easy. The approval is the job.
Reading an invoice is solved. What costs a finance team its month is the chasing, the second signature and the one nobody answered.
Three ways out of one step
Approved, declined, or nobody answered
The third is the one that costs you the week, so it is a path the process owns rather than a reminder somebody has to remember.
Approval step
Invoice over threshold
Assigned to the people your policy names, with a deadline on it.
Approved
approve
Carries on to the next step with the decision kept against the invoice
Declined
decline
Goes back with a reason attached, not as a forwarded email
Nobody answered
deadlineNotifications
A deadline fires its own notifications rather than waiting on a chaser
Who has to say yes
One approver, all of them, or most of them
The rule is part of the step, so a policy that needs two signatures does not depend on somebody remembering it needs two.
Any
The first approver to answer decides it. Good for low-value invoices.
All
Everyone named has to approve. Used where a second signature is the policy.
Majority
More than half carries it, so one person being away does not stall the run.
Any, All and Majority are the modes a group approval supports.
What starts it
A process begins on an event, not a reminder
Whichever of these happens first is the one that sets the invoice moving.
- Someone uploads itCapture
- A form is submittedFormSubmission
- Indexing is committedCommit
- A task is completedTaskCompletion
- Tags changeTagsUpdate
What it can do next
Each step is one of these
Strung together in the order your approval policy actually runs in.
Ask for approval
Approval
Ask a group
GroupApproval
Send an email
Email
Raise a task
Task
Move it
FolderChange
Rename it
DocumentRename
Make a document
DocumentFromTemplate
Approved invoices reach QuickBooks or your ledger through Zapier or the public API, which are integrations rather than native connectors. Paige and CapturePoint read the invoice before it lands.
FAQ
Accounts payable questions
Yes. A group approval can require any one approver, all of them, or a majority, so the rule matches your policy rather than forcing a single approver on every invoice.
An approval step can carry a deadline, and the deadline has its own notification path, so chasing is something the process does rather than something a person remembers to do.
Yes, through Zapier or the public API. A document landing in a project fires a trigger, and the Zap carries it on to QuickBooks or whatever you use. These are integrations rather than native connectors.
Paige reads incoming invoices, classifies them and pulls the values off them before they land. CapturePoint does the same where the paper is measured in boxes.
Run one month of invoices through it
Create a free account, build the approval rule your policy already has, and let the deadline do the chasing.
Prefer to talk? Call (863) 937-0272