---
title: "Reconcile clinic appointments, invoicing and payments · Lyntev"
description: "Cross-check completed consultations, documents and payments without confusing scheduling with invoicing. Includes exceptions, a reconciliation example and a closing worksheet."
url: "https://lyntev.com/en/guides/reconcile-clinic-appointments-invoicing-payments"
language: "en-GB"
date_published: "2026-11-21T17:20:13.047Z"
date_modified: "2026-11-21T17:20:13.047Z"
---

1. [Home](<https://lyntev.com/en>)
2. [Practical guides](<https://lyntev.com/en/guides>)
3. How to reconcile a clinic’s appointments, invoicing and payments received

# How to reconcile a clinic’s appointments, invoicing and payments received

A booked consultation may not have taken place; a completed one may await document checks; an invoice may remain unpaid. Administrative reconciliation cross-checks these events and explains differences. This guide proposes a checking routine without replacing the clinic’s tax framework, accounting or appropriate invoicing software.

By [Lyntev](<https://lyntev.com/en/company>). Updated on 20 November 2026.
About 5 minutes to read.

[Start reading](<https://lyntev.com/en/guides/reconcile-clinic-appointments-invoicing-payments#leitura>)[Download worksheet](<https://lyntev.com/recursos/en/reconciliar-agenda-faturacao-clinica.txt>)

**From data to the next decision**Choose the question, define the calculation and act on the result.

Translation published on 21 November 2026. [Original Portuguese guide](<https://lyntev.com/guias/reconciliar-agenda-faturacao-clinica>); source revision 20 November 2026.

By the end, you can:

- Separate completed, invoiced and received
- Find differences using checkable references
- Close the period without duplicating documents or payments

In this guide

1. [Define three records that do not mean the same thing](<https://lyntev.com/en/guides/reconcile-clinic-appointments-invoicing-payments#acontecimentos-diferentes>)
2. [Link by reference and keep clinical data out of reconciliation](<https://lyntev.com/en/guides/reconcile-clinic-appointments-invoicing-payments#mapa-de-ligacoes>)
3. [Check lines before drawing conclusions about the total difference](<https://lyntev.com/en/guides/reconcile-clinic-appointments-invoicing-payments#exemplo-de-fecho>)
4. [Classify exceptions without creating documents to make totals match](<https://lyntev.com/en/guides/reconcile-clinic-appointments-invoicing-payments#excecoes-explicadas>)
5. [Close in stages and allow time for open differences](<https://lyntev.com/en/guides/reconcile-clinic-appointments-invoicing-payments#ordem-do-fecho>)
6. [Test partial payments, repetitions and late corrections](<https://lyntev.com/en/guides/reconcile-clinic-appointments-invoicing-payments#testar-reconciliacao>)
7. [Take the worksheet to the demonstration and accounting team](<https://lyntev.com/en/guides/reconcile-clinic-appointments-invoicing-payments#ficha-fecho-clinica>)
8. [Sources and criteria](<https://lyntev.com/en/guides/reconcile-clinic-appointments-invoicing-payments#fontes>)

## Define three records that do not mean the same thing

The calendar shows planning and service states. Invoicing documents operations under applicable rules. Payment records track money actually paid or received through the method used. Autoridade Tributária distinguishes an invoice from a receipt; the clinic’s tax lead should define documents for each specific situation, including advance payments and corrections.

Do not assign “paid” because an invoice exists or mark a consultation completed merely because there was an advance payment. Keep the appointment identifier, document reference and financial movement reference in separate fields. One service may relate to several payments and a document may cover a scope needing its own check. The procedure should explain these relationships before automating totals.

## Link by reference and keep clinical data out of reconciliation

Choose identifiers that relate records without exporting clinical history. For administrative reconciliation, the service reference, date, provider, state and necessary amounts may suffice. Do not include diagnoses or restricted notes in a financial file simply because they are available in the same system. Define who may consult and correct each field.

For a manual connection, use one checked-reference column and another for exceptions. For an integration, request a demonstration of what happens when a message repeats or arrives out of order. A link between two programs does not guarantee the operation has been validated. Keep the import result and checking time to distinguish data not yet received from data genuinely missing.

## Check lines before drawing conclusions about the total difference

In a fictitious scenario, service A is completed, has a 70 € document and a 70 € payment received. B is completed and documented for 100 €, but only 40 € has been received; a 60 € difference requires clarification under the case’s conditions. C is cancelled and has a recorded advance payment requiring the validated treatment for that situation.

Simply adding documents and comparing payments would produce an unexplained difference. Separate amounts to check, genuinely confirmed debt, advances and pending corrections. A discrepancy does not automatically prove patient non-payment or a system error. The person responsible should locate movements and check dates, references and scope before contacting anyone or correcting documents.

Check lines before drawing conclusions about the total difference

| Fictitious case | Calendar | Document / payment received | Next check |
| --- | --- | --- | --- |
| A | Completed | 70 € / 70 € | Complete references and matching |
| B | Completed | 100 € / 40 € | Confirm the nature of the remaining 60 € |
| C | Cancelled | Existing advance payment | Apply approved tax and commercial procedure |
| D | Awaiting confirmation | No relationship identified | Clarify the service before concluding |

## Classify exceptions without creating documents to make totals match

Prepare categories such as missing reference, partial payment, third-party payment, document from another period, pending correction and service awaiting confirmation. Each category should have a person responsible and the information needed to resolve it. Do not invent an invoice or receipt to eliminate a visual difference; issue and correction follow the authorised process and actual situation.

Where insurers, agreements or paying entities exist, separate contractual provisions from what was actually confirmed. This guide does not define those relationships’ rules. Reception should refer a discrepancy with necessary identifiers without promising a final amount before validation. Preserve history when a line changes classification so the original closing and later resolution can be explained.

## Close in stages and allow time for open differences

Choose a known period and cut-off time. First confirm calendar states with those competent to validate them; then check documents and payments received through their identifiers. List differences without erasing them from the period. Distinguish provisional administrative closing, completed checking and accounting processing rather than using the same word for different tasks.

The following week, start with old exceptions and record what was resolved. A late correction needs its own date and reference; it should not silently rewrite a listing already delivered. Agree with accounting which files or reports are needed and a secure sharing channel. Also define who authorises changes to already checked payments so the process does not depend on a shared account without identifiable responsibility.

## Test partial payments, repetitions and late corrections

Prepare fictitious data for full payment, partial payment, an advance, cancellation, a corrected document and a repeated movement. Calculate the expected result outside the system and ask two people to check the same period using the written rule. Differences reveal unclear definitions, such as using the service date in one listing and payment date in another without explaining the choice.

Acceptance criteria: no payment received is counted twice, every amount has an origin, differences are assigned and totals are reproducible under the same rules. An administrative role should not consult clinical notes to complete the operation. If a system exports only totals, request more detail before relying on closing. A correct sum can hide two opposite errors cancelling each other out.

## Take the worksheet to the demonstration and accounting team

Clínicas Pro includes accounts receivable, accounts payable and management reports. It does not replace certified invoicing for clinical procedures. When assessing the product, confirm the process with the invoicing software used rather than assume an undemonstrated automatic integration. If reconciliation is manual, it should remain explicit in the process and planned team effort.

Use the worksheet to align reception, administration and accounting. The clinic defines the appropriate framework and permissions. Review the procedure when a payment method, paying entity or program changes. The aim is to explain every difference and its resolution while keeping health information separate from financial work that does not require it.

### Worksheet for your project

```
Clinic administrative reconciliation worksheet
Period, cut-off time and rules version:
Person responsible for service states:
Appointment identifier and checked state:
Tax-compliant invoicing software and document reference:
Method, date, reference and amount received:
Partial, advance or third-party payments:
Difference and provisional classification:
Person validating the framework and appropriate document:
Next action, person responsible and review deadline:
Later correction and link to the original movement:
Exported data and access roles:
Reproduced totals, open exceptions and approval:
```

## Sources and criteria

Content prepared with AI assistance and research using technical sources, with checks of the relevant examples and calculations. The references support the guide’s decisions; examples identified as fictitious let you try out the method.

- [Autoridade Tributária — Fatura e recibo](<https://info.portaldasfinancas.gov.pt/pt/apoio_ao_contribuinte/Cidadaos/Atividade_profissional/Fatura_e_recibo/Paginas/default.aspx>)
- [Autoridade Tributária — Regras de faturação](<https://info.portaldasfinancas.gov.pt/pt/apoio_ao_contribuinte/Negocios/Faturacao/Regras_de_faturacao/Paginas/default.aspx>)
- [CNPD — Diretriz/2023/1 sobre medidas organizativas e de segurança](<https://www.cnpd.pt/umbraco/surface/cnpdDecision/download/122048>)

## Continue to your next decision.

- [Define team permissions](<https://lyntev.com/en/guides/define-team-permissions>)
- [Run the weekly operations meeting](<https://lyntev.com/en/guides/run-weekly-operations-meeting>)
- [Explore Clínicas Pro](<https://lyntev.com/en/clinic-management-software>)

This guide is part of [Prepare your clinic’s workflows.](<https://lyntev.com/en/guides#gestao-clinicas>)

- [How to manage cancellations and rescheduling at a clinic](<https://lyntev.com/en/guides/clinic-cancellations-rescheduling>)

[Explore the guide library](<https://lyntev.com/en/guides>)

## Put this decision into practice.

Steps, examples and worksheets to prepare the work in your business.

[Find a reading path](<https://lyntev.com/en/guides#percursos-title>)

### [How to manage cancellations and rescheduling at a clinic](<https://lyntev.com/en/guides/clinic-cancellations-rescheduling>)

Close the request when the new arrangement is confirmed and dependencies have been reviewed.

### [How to keep customer service organised when the Internet fails](<https://lyntev.com/en/guides/customer-service-internet-outage-continuity>)

Prepare the alternative, limits and reconciliation before an interruption.

## Would you like to apply this to your business?

Send us your worksheet or explain what you need to improve. We help you choose the next step for your project.

- [Lyntev assistant Immediate answers about services, prices and timescales, with a cost estimate. Read the assistant guide](<https://lyntev.com/en/help/ai-assistant>)
- [WhatsApp +351 928 412 891. The message is only sent when you confirm it in WhatsApp. Write on WhatsApp](<https://wa.me/351928412891?text=Hello!%20I%20came%20from%20the%20Lyntev%20website%20and%20would%20like%20to%20discuss%20a%20project.>)
- [Form Describe what you need and receive the reply by email. Complete the form](<https://lyntev.com/en/contact>)
- [Email contacto@lyntev.com Send an email](<mailto:contacto@lyntev.com?subject=Request%20for%20information>)

![Wellinton Oliveira](<https://lyntev.com/media/autores/wellinton-oliveira.webp>)

Written by

[Wellinton Oliveira](<https://lyntev.com/en/company>)

CEO of Lyntev

Technology with context, original analysis and sources you can consult.
