Business proxy services: contracts, invoices, acceptance acts, and EDI
Technical delivery and business documents should describe the same service: period, quantity, tariff, acceptance process, and responsible parties.
Key points in one minute
- Each business transaction requires a primary accounting document with mandatory details.
- Choose the EDI format and operator before the first bulk exchange.
- Documents should reconcile with actual technical delivery and period.
- A repeated payment notification must not alter the balance twice.
Service scope
The agreement or offer should define access type, term, quantity, rotation, support, acceptable use, load limits, and suspension procedure.
Link legal wording to measurable portal objects: order ID, lease period, quantity, tariff class, available actions, support hours, and service-start criterion. Upstream providers and internal EIDs may remain implementation details, but replacement, downtime, renewal, and termination procedures should be clear. State acceptable use specifically and enforce it consistently across customers.
Invoice and payment
Link the invoice to an order and payer. Payment status should not imply successful technical delivery without separate confirmation.
The financial ledger should keep an immutable link among invoice ID, order ID, payer, amount, purpose, status, and external payment identifier. Replayed bank notifications must not create a second credit. If payment is confirmed while delivery has an unknown outcome, move funds and order to reconciliation; the system must not repurchase or charge again to hide a technical failure.
Acceptance and primary documents
The document should reflect the actual service period and volume and include mandatory details. Corrections follow an approved process.
Generate primary accounting documents from actual service periods and quantities, not only the original order. Mandatory details, document form, issue date, and correction process should follow the accounting policy and current requirements. Before signature, reconciliation should detect mismatches across order, technical delivery, payment, and act while preserving a clear correction trail.
EDI and retention
Check the operator in the Federal Tax Service registry, interoperability, signatures, and format. Retain primary documents and related evidence for the required period.
Before bulk EDI, verify the operator's current official-registry status, format, signature type, signatory authority, interoperability route, and delivery receipts. One test package should cover sending, receipt, signing, correction, and archival reopening. Store the original document, signature, and technical confirmations together; a printout is not a substitute for validating the electronic original.
Practical checklist
- 1Reconcile tariff across order, invoice, and act.
- 2Define the acceptance process.
- 3Test EDI with one document.
- 4Link order, invoice, payment, and act IDs.
- 5Run a complete EDI test cycle.
Sources and documentation
This material is based on primary, official, and technical sources. The article is an original summary written for this knowledge base.
This material is for general information only. Requirements should be checked against the current law and, when needed, with a qualified specialist. It is not individual legal advice.
- 1.Официальный интернет-портал правовой информации: Федеральный закон от 06.12.2011 № 402-ФЗ «О бухгалтерском учёте» — первоначальная официальная публикация
- 2.ФНС России: Перечень операторов электронного документооборота
- 3.Президент России: Базовый текст Федерального закона от 27.07.2006 № 152-ФЗ «О персональных данных»