Integrations & data · Practice guide

Connect each payment to its invoice or booking

Illustrative situation

A payment provider reports a successful transaction but staff cannot identify which invoice or booking it belongs to. Staff need to connect a payment with the right invoice or booking before acting on it. A provider reference that makes sense only in the payment account creates manual searching. Keep the business reference visible across the handover.

Healthcare booking calendars on two connected screens with blue and orange appointment cards.
Make the handover between tools clear for the team using them.

What this means for your practice

Keep a dependable reference connecting the payment with its business record. Agree who checks differences between the provider and clinic systems, while the finance team decides financial treatment.

An example to discuss with your team

Process a fictional test payment with a deliberately unmatched reference.

Healthcare data integration connecting two applications through a field-mapping board.
Agree what each field means and which system owns it.
Healthcare data validation separating matched records from an exception tray.
Make rejected or uncertain records visible for review.

Questions to take to your supplier

Ask to demonstrate an unmatched fictional payment through the provider's test arrangements. Finance should see the exception and own its resolution. Keep payment and booking states distinct: the responsible teams should define what a payment result means for the administrative journey.

Agree the working process

Agree the business reference used to connect the payment event with the record finance or reception actually works from. Keep the provider's own reference too, since it may be needed for investigation, but explain the relationship in the staff view. Decide which team handles unmatched events and what information they need to resolve them through the approved process. A payment result and an appointment result should remain distinct unless the business has explicitly defined their relationship. For example, the team may need to review a successful test payment whose related administrative record was not created.

Use that situation in acceptance, alongside an ordinary matched result. Ask how later provider updates are connected to the same history rather than creating another apparent payment. Your finance team should define accounting treatment and approval responsibilities. Review the exception list with that team, looking at age and causes as well as count. An integration is more useful when the practice can explain each unresolved event than when it merely reports a high proportion of automatic matches.

How to check the result

Count payment events still waiting to be matched or explained by the responsible team.

Turn reading into a next step

Your action checklist

Work through these checks with your team or supplier. Tick the ones you have resolved and leave unknowns open.

Checks to discuss

Record what you know, what is still missing and the answer you need from your team or supplier.

Use project decisions only, without personal, patient or confidential details. Entries stay in this page and are not submitted to Kay & Co. Copy or download before leaving; this page does not save your notes.

Further reading

These sources provide background for the topic. The practice examples and checklist are illustrative planning suggestions from Kay & Co.

Related guides

Need help with this?

Tell us what is getting in the way. Kay & Co. can help you understand the options and turn the next step into something that works for your practice.

Explore integrations & data services or discuss your project.

Try the free Healthcare Digital Planner to find your starting priority.