Read an Obedience invoice

Purpose and scope

Check supplier details, line items, tax treatment, status and payment reference before processing an invoice.

Use this guide as orientation, then rely on the signed agreement, current policy or named support response where those sources set a more specific obligation.

Prepare the right information

• The issued invoice and version.
• The applicable order or agreement.
• Tax and payment details already held through an approved channel.

Follow the controlled process

1. Frame the needState the desired outcome, affected product and accountable contact. For read an obedience invoice, avoid assumptions that have not been confirmed in writing.
2. Review and decideUse the current governed source, record material questions and obtain approval from the person who owns the decision.
3. Retain evidenceKeep the final reference, date, decision and any follow-up action together so a later reviewer can reconstruct what happened.

Expected record

• A validated invoice.
• A traceable payment reference.
• Any discrepancy raised before payment.

Security and disclosure boundary

• Never send passwords, authentication codes, private keys or recovery codes to Obedience staff.
• Share the minimum customer, project and commercial information needed for the stated purpose.
• Public documentation explains controls and responsibilities without publishing exploitable topology, credentials or confidential implementation detail.