BDI

Defense technology.
Buyers, markets, opportunities.

Preparing a DC4 declaration before a French public subcontract begins

Align the proposed subcontract, DC4 declaration, approved payment conditions and later payment request before committing a specialist supplier to French public-contract work.

In this article
  1. Connect the declaration with the subcontract
  2. Agree the amount and the payment assumptions together
  3. Establish whether direct payment applies to this relationship
  4. Treat acceptance and the payment request as separate stages
  5. Keep changes aligned with the approved arrangement
  6. Make the invoice follow the established relationship
  7. Sources & evidence

A proposed French public-contract subcontract should have a clear scope, an identified contracting relationship and a documented payment arrangement before the specialist supplier treats it as confirmed work. The DC4 supports that process by presenting the subcontractor and its terms to the public buyer. It should reflect the commercial agreement being made, rather than becoming an administrative form completed after delivery has already begun.

The immediate supplier decision is whether the proposed work and payment position are sufficiently defined to commit staff and costs. A positive conversation with the main contractor is useful, but finance and operations need the actual arrangement they are being asked to support.

Connect the declaration with the subcontract

The DAJ's DC4 explanatory notice describes the identification of the subcontractor, the services subcontracted and the payment conditions. It explains the buyer's acceptance of the subcontractor and approval of those conditions. The notice also distinguishes requirements according to the contract and the supplier's place in the subcontracting chain.

Consider a hypothetical company providing translation for a public institution's training contract. The main contractor wants it to translate course materials, but initial discussions also mention later updates and attendance at workshops. Those tasks could require different resources. The parties should settle which services belong in the proposed subcontract before the scope is presented for approval.

Write the scope so that a colleague can identify the expected output and its boundary. A description limited to “language support” leaves too much room for different expectations about review rounds, document volumes and participation in meetings. The declaration and the commercial agreement should refer to the same proposed work.

Our explanation of French groupements and co-traitance covers the alternative situation in which companies submit a joint offer. The translation company's role here is a subcontract relationship with the main contractor. Its paperwork and commercial analysis should reflect that role consistently.

Agree the amount and the payment assumptions together

The amount shown in the declaration should connect with a scope and price basis that both parties understand. If the translation business prices a defined set of materials, identify what happens commercially if the quantity changes. A broad maximum should not conceal a disagreement about the services included in the underlying price.

For internal planning, the supplier can prepare a short bridge between its quotation, the agreed subcontract and the declaration. It should show the amount, the services it covers and any specified price-adjustment mechanism. This makes it easier to identify a mismatch before a finance colleague relies on the record for invoicing.

The DC4 notice addresses payment conditions and bank details as distinct information. The supplier should check both, while keeping changes to banking instructions under its established verification process. Correct payment routing cannot resolve an unclear contractual entitlement, and an agreed price cannot compensate for an inaccurate recipient record.

Suppose the translation business expects two delivery stages but the main contractor has assumed one final invoice. Both approaches might be workable, yet they imply different cash commitments for the subcontractor. Resolve the difference before mobilising the team and make the eventual agreement clear in the documents supporting the arrangement.

Establish whether direct payment applies to this relationship

The DC4 notice identifies direct payment as a conditional arrangement for first-tier subcontractors and describes specific treatment for defence and security purchasing. That is a reason to examine the applicable contract and provisions before assuming that any subcontract declared on DC4 will be paid directly by the public buyer.

The translation company should ask its bid owner to establish the proposed payment route using the actual documents. Identify the public contract, the subcontracting tier, the relevant approved terms and the person who will handle payment requests. Put the resulting arrangement into the cash forecast with the evidence supporting it.

This assessment is particularly important where the business supplies another subcontractor rather than the main contractor. The fact that work ultimately supports a public contract does not make every company in the chain commercially interchangeable. The supplier needs to know which business owes it payment and what protection or process applies to its own agreement.

Once the route is established, operations should know which delivery records finance will need. For the translation work, that might mean a list of delivered files, the version supplied and confirmation of the completed stage. Agreeing this evidence early reduces the risk of a payment query becoming a retrospective search through project correspondence.

Treat acceptance and the payment request as separate stages

Acceptance of a subcontracting arrangement does not remove the process for requesting payment for the work. Article R2193-12 gives the main contractor fifteen days from the specified receipt event to agree or notify refusal of the subcontractor's payment request. The relevant request and receipt records therefore matter alongside the approved subcontract.

The DAJ's account of the Conseil d'État's October 2023 decision explains the effect of a timely reasoned refusal by the main contractor on the public buyer's direct payment. The practical lesson is to follow the applicable request procedure and address a substantive disagreement through the appropriate route, rather than assuming approval of the subcontract settles every later invoice.

For the hypothetical translator, a request should describe the completed stage in the same terms as the subcontract. If the main contractor disputes whether a final revision was included, the parties need the agreed scope and the delivery record. A clearer request can help isolate that issue; repeatedly sending the same unexplained amount does not resolve it.

Keep the date and evidence of receipt with the request. Finance should be able to distinguish a draft invoice prepared internally from a request actually received through the required route. That distinction helps the company understand which stage has been reached and what action is appropriate next.

Keep changes aligned with the approved arrangement

During delivery, the public buyer or main contractor may identify additional work. The translation business should establish whether it is being asked to revise the existing package or quote a separate task. A project conversation should be translated into the appropriate commercial process before staff assume that the original arrangement covers the extra effort.

Maintain a record connecting changes in scope with changes in amount and payment expectations. Where the declaration or approval needs updating, coordinate that step through the responsible contractor and buyer process. The objective is a consistent account of the work being performed and the sums associated with it.

The supplier can make this manageable by assigning one commercial owner for the subcontract. Project staff report a proposed change to that person, who checks the agreement and establishes the next step. This allows delivery specialists to focus on their work while avoiding informal commitments that finance cannot reconcile later.

Make the invoice follow the established relationship

Before the first payment request, compare the supplier identity, contract reference, approved scope and expected supporting records. Check who must validate the request and what system or channel is specified. The guide to Chorus Pro invoice progress explains why submission, processing and payment are separate events in the French public-sector workflow.

For the translation company, a well-prepared subcontract file should allow a new finance colleague to identify the work, the payment route and the evidence behind each request. That is the useful result of treating DC4 as part of commercial preparation. It gives the business a clearer basis for committing resources, managing changes and following the money through the relationship it has actually agreed.

Sources & evidence

  1. DC4 explanatory noticeDirection des affaires juridiques
  2. Article R2193-12Légifrance
  3. Direct payment and a reasoned refusal by the main contractorDirection des affaires juridiques

DAJ DC4 guidance, current article R2193-12 and the DAJ account of the October 2023 Conseil d’État decision were directly read on 6 September 2026. Direct-payment discussion remains conditional on tier and applicable procurement provisions. The translation subcontract is hypothetical.

Suggest a correction