Track Recurring Maintenance Visits Without Duplicate Invoices

Practical answer: Distinguish scheduled visits, repeated invoice numbers and forwarded copies across a service contract.

Monthly or quarterly service visits naturally produce similar documents. A duplicate check based on supplier and amount alone can delete a legitimate visit, while email forwarding can create several copies of the same invoice.

Anchor each visit to a service period

Record service date, covered asset, contract reference and invoice number. If the provider reuses numbering patterns, the service period and source file become essential comparison evidence.

Compare exact copies separately from repeated services

Check document content, invoice identifier, dates, amount and attachment source. A forwarded PDF may be identical; two scheduled visits may share the same amount but show different service dates.

• Retain revised invoices with an explicit relationship.
• Do not delete solely from amount matching.
• Keep the duplicate decision in a review note.

Use the recurrence pattern to find gaps

Sort completed records by contract and period. A missing quarter, late invoice or unreviewed visit becomes visible without fabricating an expense for an expected document.

Recurring service controls

• Every visit has a supported service period.
• Duplicate decisions compare several fields and the source.
• Revisions remain traceable.
• Expected but missing invoices stay visible as gaps.

Questions people ask in this situation

Can recurring invoices share one category?

Yes, while dates, invoice identifiers and source documents still keep each service event distinct.

Should an expected invoice be created manually?

No. Track it as missing or pending until a real source arrives.

Where AI Expense fits

AI Expense search and structured fields can reveal recurring patterns while source access supports safer duplicate review.