How a French Micro-Entrepreneur Can Invoice a US Client

Start Here and Build a Risk-First Invoicing System#

Start with compliance, then protect cashflow. If you work from France under the micro-entrepreneur regime and bill a US client for services, one reliable way to create delays is to optimize payment collection before your invoice and records are in order.

That matters because micro-entrepreneur status is simplified, not informal. The regime reduces administrative weight, but it still comes with core accounting rules. One of the first obligations is keeping a revenue book, and that register should be accurate and up to date. In practice, each paid invoice should be traceable to the customer or company identity and the nature of the transaction, not just a number in your bank feed.

What risk first means here#

A risk-first setup is simple: every invoice should survive three checks before you send it:

If a payment later arrives short, late, or from the wrong remitter, those three checks give you something solid to work from.

Build one pre-send checklist, then stop improvising#

You do not need a fancy tool stack. You need one repeatable checklist for every international invoice. The useful version is short enough to use every time and strict enough to catch preventable mistakes when you are under deadline pressure. A practical pre-send checklist looks like this:

1. Confirm the client legal entity and billing contact.
2. Match the invoice to a dated service period or deliverable.
3. Check your invoice wording and numbering before export.
4. Save the final PDF where you can find it later.
5. Record the expected amount and payer name so you can match the payment when it lands.

Be blunt about it: if any one of those items is unclear, pause before sending. Fixing an invoice after a client has already routed it for payment can take longer than spending a few extra minutes up front.

Keep a monthly evidence routine#

Your monthly routine should be boring and repeatable. For each client, keep the invoice PDF, the supporting commercial document if you used one, and the payment proof together. Then update your revenue book so the customer identity and transaction nature are recorded while the details are still fresh.

One more point to watch. France's e-invoicing and e-reporting reform is rolling out on a domestic B2B timeline. Large and mid-sized companies start in September 2026, and SMEs and micro-enterprises follow in September 2027. Treat that as a separate compliance horizon to monitor, especially if you also bill French businesses. It is not a reason to overcomplicate your current cross-border process, but it is a reason to keep your records clean now.

We covered this in detail in A Canadian Corporation's Guide to Invoicing a US Client.

Understand the Terms Before You Change Anything#

Start from the French rules, not the client template. The Micro-entrepreneur (Auto-entrepreneur) setup is simplified, but it is still tied to specific tax and social obligations in France.

If your US client is a business, you still issue an invoice for each service. French invoice formalities still apply when you bill a foreign client, so cross-border does not mean informal.

You may hear Entreprise Individuelle (EI) used as a business label. Treat it as context, not as a shortcut around invoice requirements: keep mandatory invoice mentions in place, and check that your invoice timing matches service completion before you send it.

Use TVA as a checkpoint, not an assumption. Do not assume "US client = no French VAT issue," and do not reuse tva non applicable wording unless you have confirmed it fits the case.

If you are considering a US sole proprietorship, LLC, or PLLC, pause and verify invoicing and reporting implications before changing structure. Complexity often shows up first in invoice wording, payee identity, and record consistency. For more background, see A Guide to France's Micro-Entrepreneur Regime for Freelancers.

Build a Compliant Invoice Core Before You Optimize Payments#

Before you optimize payment rails, lock a repeatable invoice workflow: validate client details, draft, verify VAT wording, then send. Keep that order even when payment feels urgent.

Use one pre-send checklist every time#

Use one checklist for each international invoice so your process stays consistent under pressure:

• Confirm the client's legal name and billing country.
• Draft from your own invoice template.
• Verify mandatory invoice mentions and the "TVA non applicable" mention only when relevant.
• Confirm invoice numbering is consistent (no duplicate or skipped number).
• Add an evidence attached checkpoint before sending.

Urgency should change speed, not controls.

France's e-invoicing reform is a progressive transition with regulatory and technology obligations. It is also described as moving invoice exchange through distinct paths (PPF and approved PDPs), with paper invoices beginning to phase out in 2026. So even if a client still accepts PDF by email today, a disciplined digital invoice record is the safer base.

Quote and invoice are not the same document#

Treat the quote (devis) as the commercial offer, and the invoice as the payment request tied to an agreed billing trigger in your written agreement. Before you convert a quote into an invoice, make sure the billed scope, service period, and trigger are clearly aligned with what was accepted.

If that basis is unclear, pause and fix the paperwork first.

Add evidence before sending, not after a dispute#

A compliant invoice is easier to defend when the evidence is attached at send time. At minimum, confirm the service period, a deliverable or milestone reference, and the payment terms shown on the invoice.

This keeps payable reviews faster and reduces avoidable back-and-forth later.

Decide VAT Handling With Clear If-Then Rules#

Treat VAT handling as a recurring decision, not a one-time setup. If the service changes, the billed client entity changes, or the billing route changes, re-check French VAT treatment before you send the next invoice.

That discipline matters because French invoicing is treated as strict on VAT and timing, and invoices to business clients are generally mandatory for each service sale. For services where the client is liable for VAT, invoicing is typically tied to service completion, with a cited deadline by the 15th day of the following month.

Keep the VAT field controlled#

Keep "TVA non applicable" as a controlled field in your template, not free text you rewrite from memory. Manual rewrites create stale-wording risk and a weak audit trail.

Before you send, verify these four points against one VAT decision note in your client record:

• billed client legal entity
• client country
• service description on the invoice
• date VAT treatment was last checked

If any of these changed, treat the prior VAT decision as outdated and re-validate before issuing the invoice.

Separate known cases from unknown ones#

What the current source pack clearly supports: VAT invoicing and deadlines are treated as strict; invoice timing matters; and France is moving to phased mandatory e-invoicing/e-reporting in 2026-2027, with structured formats (such as Factur-X or XML) and transmission through public infrastructure.

What it does not pin down: the exact legal trigger formula for when "TVA non applicable" applies in your specific case, and regime-specific VAT exemption logic for every micro-entrepreneur scenario. If your case is unusual, note the uncertainty and get professional confirmation before you change invoice wording.

Use one escalation trigger#

Set one hard stop: if your activity or client model shifts, pause billing changes until VAT treatment is validated. Typical triggers include changing from services to goods, adding a platform intermediary, billing a different entity, or changing what the quote and invoice describe.

If the facts changed, pause, validate, then invoice. That short delay is usually cheaper than fixing tax wording after approval or payment.

Choose the Right Billing Entity Without Creating Tax Friction#

Start with your existing French setup unless the client can show a real blocker. If you already bill as a Micro-entrepreneur or Entreprise Individuelle (EI), treat direct invoicing as the default and only add a US sole proprietorship, LLC, or PLLC when there is a clear operational reason.

The tradeoff is straightforward: an extra entity can satisfy some client workflows, but it usually adds more moving parts across classification, tax and social rules, payment method setup, and risk management. Keep that full complexity in view before you restructure.

Test the blocker before changing entities#

If the request is "we prefer US vendors," confirm what is actually required:

• exact legal name they need on the contract and invoice
• whether the issue is vendor onboarding, payment rails, or contractor classification
• whether they are asking for a document in their file versus a different billing entity
• whether your current French billing setup already meets their process

Keep US-side forms separate from French invoice duties#

You may be asked for W-8BEN or hear references to 1099-NEC in US accounts payable workflows. In this section's source pack, those forms are not presented as proof that you must change your French invoicing setup or create a US entity.

Operationally, treat form requests as document workflow items: capture the request in writing, store what you submit, and review your invoice fields separately if your billing facts change. If you do add a US entity, align everything at once: contract party, invoice issuer, payment instructions, and your VAT decision record.

This pairs well with our guide on How to Invoice a UK Client to Avoid VAT Complications Post-Brexit.

Pick Payment Rails Based on Risk Not Convenience#

Pick the rail that fails in the least damaging way for your cashflow. If holds, disputes, or reconciliation gaps are already a problem, prioritize clear status tracking and evidence quality over setup speed.

Your invoice duties do not change by rail. You still need a complete file for each invoice and payment outcome, whether payment comes through PayPal, an invoice link, or bank transfer.

Compare rails by operational risk#

PayPal requires active fee checks, not memory-based assumptions. Pricing depends on method, and PayPal says changes are tracked on its Policy Updates Page. Also treat market classification carefully: PayPal defines an international transaction as sender and receiver in different markets, which is relevant for France-to-US payments.

Invoice-link flows are most useful when you need tighter payment-status tracking and faster reconciliation. If you use Gruv invoice collection and status tooling where enabled, you can centralize invoice state and audit-ready records; coverage varies by program.

Set failure ownership before first payment#

For a practical default: use invoice-linked collection when visibility and reconciliation are your main risks, use bank transfer when remittance discipline is strong, and use PayPal only after checking current method-based fees and accepting dispute overhead.

Need the full breakdown? Read The Best Way to Invoice a Canadian Client from a US LLC to Minimize Fees.

Lock In Contract Terms That Prevent Late or Bad Payments#

Late or bad payments are usually a terms problem before they are a payment-rail problem. Your invoice record helps, but it will not fix unclear scope, weak acceptance steps, or payment timing the client never clearly accepted.

Use your freelance contract to make the key points unambiguous:

• payment window
• scope boundaries and out-of-scope handling
• included revision rounds
• late-payment policy, stated explicitly and mirrored on the invoice

Use the devis as your first payment control#

Treat the Quote (devis) as a pre-invoice approval checkpoint. Before delivery starts, get written acceptance and make sure the devis and contract match on scope, price, delivery format, and billing rhythm.

Before issuing the first invoice, run a quick consistency check across the accepted devis, contract, and invoice draft:

• client legal name
• project description
• currency
• payment timing

Set terms by cash buffer, not optimism#

If proposed net terms exceed what your cash buffer can absorb, change the structure instead of hoping collections stay on track:

• require milestone billing for longer terms
• request partial upfront payment for front-loaded or custom work
• tie invoices to clear approval events or named deliverables when phases are ambiguous

Pause when paperwork is inconsistent#

Pause work if any of these appear:

• missing signer or no clear approver
• unclear acceptance criteria
• conflicting billing instructions across the contract, purchase order, or email

Then assemble one working file before proceeding: signed contract or accepted devis, final scope summary, acceptance method, billing contact, and remittance instructions. Keep that file aligned with your invoice records so payment follow-up is faster and cleaner.

Run a Monthly Evidence and Reconciliation Routine#

Run this once a month so each client month closes with one clear record: what you invoiced, what you received, what fees were deducted, and why any gap exists.

Keep an invoice retention folder by client and month, with consistent files each time:

• invoice PDF
• signed contract or accepted devis
• proof of payment
• snapshot of the VAT wording used on that invoice (including "TVA non applicable" when relevant)

Before you mark the month complete, confirm the key fields match across files: invoice number, client legal name, amount, currency, and payment date.

Write exception notes immediately. If the net is short, record the reason while the trail is still clear.

Keep cross-border paperwork in the same monthly structure but separate from the invoice record. If a client requests a W-8BEN or shares a 1099-NEC reference, save the latest document or email thread with the date sent or received. This keeps your core invoice evidence clean while your cross-border artifacts stay traceable as France continues its phased B2B e-invoicing and e-reporting rollout.

Related reading: A US consultant's guide to invoicing a Swiss 'GmbH'.

Use One Repeatable Checklist for Every New US Client#

Use the same checklist for every new US client so each invoice cycle is lower risk than the last. Keep this sequence as your operating default: compliance first, VAT second, entity choice third, payment rail fourth, with contract controls throughout.

Follow the same pre-send sequence every time#

1. Compliance first

Confirm the client record and your seller details before drafting the invoice.

1. VAT second

Validate the VAT treatment for this specific invoice, then apply wording only after that check.

1. Entity choice third

If a client asks for a different contracting entity, pause and confirm before you change your setup.

1. Payment rail fourth

Decide the payment rail before sending so invoice terms and reconciliation expectations match the way funds will move.

1. Contract controls always

Keep payment terms explicit in writing. A practical structure is to separate charges and payment, late payments, and VAT as distinct points.

If any detail is unclear, stop and confirm before sending. A short validation step is cheaper than fixing a compliance or cashflow issue later.

Reuse one monthly reconciliation routine#

Run the same monthly review for every client: match what you invoiced, what arrived, and any differences, then keep the related records together so the flow is traceable.

France's e-invoicing timeline is also a reason to keep this routine stable and review it on schedule: one summary describes 2025 as a pilot year, with a receive obligation for all companies from September 1, 2026, and send obligations for SMEs and micro-enterprises from September 1, 2027. Use that timeline as a planning trigger to re-check your process, including any PPF or PA changes, before 2027.

For a step-by-step walkthrough, see How to Invoice a US Client from Mexico as a Temporary Resident.