Start with the sale.
Keep the amount, items and staff member with the service record. You have a useful starting point when a payment needs checking.
FOLLOW THE MONEY
The payment came in.What was it for?
A transfer alert is only one part of the story. Bring the sale, payment and shift together, so your team can check the details before calling it settled.
Built around the people doing the work.
THE WORK, MADE VISIBLE
One dinner. One payment trail.
Restaurant · evening shift
Start with the order
₦18,000
Sale recorded- Order
- #1042 · Table 08
- Recorded by
- Ada · evening shift
- Payment method
- Bank transfer
The sale gives the payment a context: an order, a team member and a shift.
Illustrative scenario · explore each step above
ONE CONNECTED PLATFORM
- Sales
- Payments
- Shift closeout
A CLOSER LOOK
A clearer trail.
A better answer.
Review the match.
Compare the source records behind a suggested match. Confirm what agrees and flag what needs another look.
Keep the decision.
A confirmation needs context. Retain the link between the payment and sale, and the record of who confirmed it.
GOOD QUESTIONS
Before you
take the next step.
A few practical details. If your setup is different, let’s talk it through.
Ask the teamDoes a suggested match mean a payment is confirmed?
No. A suggestion helps the team find records worth comparing. Review the evidence before confirming, and flag a difference when it needs follow-up.
Can this help with cash, card and transfer payments?
Innbase keeps payment records alongside sales. In your demo, we can walk through the payment methods you use and discuss the bank or provider connections your setup needs.
Where can I try an example?
The sample above shows the record trail. For a hands-on payment-match example, open the product demo on the home page and choose “Check a payment”.