Prepare the tracking of your event invoices.

List required documents before the event.

For each service, record the supplier, known references, expected documents and who receives them. Keep existing quotes and agreements with their versions; do not assume an invoice will go to the contact who received the initial proposal.

Collection may involve a deposit invoice, final invoice or credit note depending on the situation. Describe documents actually expected and deadlines agreed with suppliers; no universal deadline replaces their conditions and your internal process.

• List expected documents for each service.
• Identify the recipient and authorised channel.
• Record references required on the documents.

Check references against the invoicing process.

In France, Service Public describes general and specific invoice information, including numbers, dates, parties and service details. This French reference does not establish UK invoice requirements. Use it as a reference and have your accounts team verify requirements applicable to your situation.

The recipient identity, purchase order references, taxes and delivery channel depend on the actual process. Check electronic invoicing obligations with relevant contacts; receiving a PDF by email does not establish that processing is compliant.

Reference: Service Public Entreprendre · Required invoice information in France.

• Check the invoice recipient before issue.
• Clarify required references and delivery channel.
• Flag missing information to an authorised contact.

Match documents to the service delivered.

Link the invoice to the selected proposal, approvals and service actually delivered. Record headcount changes, additions, differences and credit notes to check. A received document is not automatically approved or paid.

In the Sourcing Force arrangement, BME purchases and reinvoices as the single supplier, tracking services, invoicing and payments after confirmation. Keep supplier processing and client invoicing separate: reconciliation must follow responsibilities and documents in the agreed arrangement.

• Track received, to check, approved or incomplete statuses.
• Identify the discrepancy and who can resolve it.
• Avoid counting deposits and the balance twice.

Assign a next action to each missing document.

Prepare simple tracking: expected document, service reference, contact, latest exchange and next agreed follow-up date. A follow-up should specify what is missing rather than requesting every document again.

Fictional example: the venue invoice has arrived, but a catering credit note is still expected after a confirmed adjustment. Keep this point open until checked; payment for another service does not close it.

• Separate missing documents from discrepancies on received ones.
• Keep a useful record of exchanges.
• Have authorised people approve exceptions.

Keep documents within the authorised process.

CNIL highlights limiting data to the purpose and arranging its security. Share documents with authorised contacts according to your organisation’s retention rules and applicable obligations.

To request support, describe services, missing document types and responsibilities in your brief. Keep accounting documents, bank details and personal data out of the AI field. The site prepares a quote request; it neither approves invoices nor triggers payments.

Reference: CNIL · Six GDPR principles.

• Define authorised access and storage.
• Ask your team which retention rule applies.
• Prepare a summary without confidential documents or data in AI.