BraiFlow CRM

Product Documentation

Operational documentation to run the platform in production: onboarding, business processes, governance and execution standards.

Country Packs

Localization and compliance by country.

Target Audience

Finance and legal teams handling country-specific e-invoicing rules.

Prerequisites

  • Country code and tax pack selected in tenant settings.
  • Company identifiers validated (VAT/SIREN/SIRET/CF).
  • Regulatory endpoint credentials available when required.

Module Positioning

Country compliance packs for invoicing, tax rules and legal formatting.

Priority Use Cases

  • Italy e-invoicing (FatturaPA / SDI).
  • France legal mentions and Factur-X readiness.

Operating Model

  • Validate legal identifiers at onboarding.
  • Run monthly compliance checks with accounting.

KPI

  • Electronic invoice rejection rate.
  • Time to correct non-compliant documents.

Recommended Path

Follow chapters in order to move from configuration to production execution.

  1. 1. Overview

    Goal: Overview

    Overview formalizes a mission-critical standard for this module.

    Expected Outcome

    After this chapter, the team can standardize "Overview" with measurable controls for regulatory compliance.

    • Country pack choice drives downstream compliance behavior.
    • Operational evidence is captured for Overview.

    Quick Validation

    Validate via UI flow and API probe (/api/v1/invoices/*), then confirm expected permissions and logs.

    • Tenant country and tax pack fields are consistent.
    • Run one positive and one negative scenario before sign-off.
    • Validate behavior with non-admin permissions.

    Risk To Avoid

    Do not move to chapter 2 before edge cases and access scope are confirmed for this step.

    • Mixing legal rules from multiple countries in one flow.
    • Skipping audit/log validation for this chapter.
    • Promoting to production without rollback path.
  2. 2. Italy: Partita IVA, FatturaPA XML, SDI

    Goal: Italy: Partita IVA, FatturaPA XML, SDI

    Italy: Partita IVA, FatturaPA XML, SDI formalizes a mission-critical standard for this module.

    Expected Outcome

    After this chapter, the team can standardize "Italy: Partita IVA, FatturaPA XML, SDI" with measurable controls for regulatory compliance.

    • Italian e-invoicing identifiers and XML schema are valid.
    • Operational evidence is captured for Italy: Partita IVA, FatturaPA XML, SDI.

    Quick Validation

    Validate via UI flow and API probe (/api/v1/invoices/*), then confirm expected permissions and logs.

    • SDI payloads pass local validation before submission.
    • Run one positive and one negative scenario before sign-off.
    • Validate behavior with non-admin permissions.

    Risk To Avoid

    Do not move to chapter 3 before edge cases and access scope are confirmed for this step.

    • Submitting XML without schema/version check.
    • Skipping audit/log validation for this chapter.
    • Promoting to production without rollback path.
  3. 3. Italy: Split, Reverse, Bollo

    Goal: Italy: Split, Reverse, Bollo

    Italy: Split, Reverse, Bollo formalizes a mission-critical standard for this module.

    Expected Outcome

    After this chapter, the team can standardize "Italy: Split, Reverse, Bollo" with measurable controls for regulatory compliance.

    • Special VAT regimes are applied by legal rule.
    • Operational evidence is captured for Italy: Split, Reverse, Bollo.

    Quick Validation

    Validate via UI flow and API probe (/api/v1/invoices/*), then confirm expected permissions and logs.

    • Split/reverse/bollo calculations are reproducible.
    • Run one positive and one negative scenario before sign-off.
    • Validate behavior with non-admin permissions.

    Risk To Avoid

    Do not move to chapter 4 before edge cases and access scope are confirmed for this step.

    • Manual overrides with no compliance trace.
    • Skipping audit/log validation for this chapter.
    • Promoting to production without rollback path.
  4. 4. France: SIREN/SIRET, TVA, mentions legales

    Goal: France: SIREN/SIRET, TVA, mentions legales

    France: SIREN/SIRET, TVA, mentions legales formalizes a mission-critical standard for this module.

    Expected Outcome

    After this chapter, the team can standardize "France: SIREN/SIRET, TVA, mentions legales" with measurable controls for regulatory compliance.

    • French legal identifiers and mandatory mentions are complete.
    • Operational evidence is captured for France: SIREN/SIRET, TVA, mentions legales.

    Quick Validation

    Validate via UI flow and API probe (/api/v1/invoices/*), then confirm expected permissions and logs.

    • Invoice preview includes all legal mentions.
    • Run one positive and one negative scenario before sign-off.
    • Validate behavior with non-admin permissions.

    Risk To Avoid

    Do not move to chapter 5 before edge cases and access scope are confirmed for this step.

    • Creating invoices with missing legal identity fields.
    • Skipping audit/log validation for this chapter.
    • Promoting to production without rollback path.
  5. 5. France: Factur-X, Chorus Pro, VIES

    Goal: France: Factur-X, Chorus Pro, VIES

    France: Factur-X, Chorus Pro, VIES formalizes a mission-critical standard for this module.

    Expected Outcome

    After this chapter, the team can standardize "France: Factur-X, Chorus Pro, VIES" with measurable controls for regulatory compliance.

    • Interoperability and transmission channels are validated.
    • Operational evidence is captured for France: Factur-X, Chorus Pro, VIES.

    Quick Validation

    Validate via UI flow and API probe (/api/v1/invoices/*), then confirm expected permissions and logs.

    • Factur-X artifacts and VIES checks are archived.
    • Run one positive and one negative scenario before sign-off.
    • Validate behavior with non-admin permissions.

    Risk To Avoid

    Do not move to chapter 6 before edge cases and access scope are confirmed for this step.

    • Treating export format as optional in regulated flow.
    • Skipping audit/log validation for this chapter.
    • Promoting to production without rollback path.

Go-live Checklist

  • Sensitive permissions are tested with a non-admin account.
  • Critical business flows are verified end-to-end.
  • Error messages are understandable and actionable.
  • An incident runbook exists for this domain.

Success Criteria

  • Faster onboarding for a new team.
  • No critical action depends on implicit tribal knowledge.
  • Support can diagnose an incident in under 15 minutes.