Are invoices released for generation & distribution?
Batch & invoice distribution status across the CREDO pipeline — where documents are stuck, how old they are, and which are missing a distribution record entirely.
0
Invoices tracked
Report
Doc status
Entity
Batches & invoices by document status
CREA (created) vs DISC (discarded) · current filter
Invoice volume by month
EU-INV insert date · matched vs unmatched groups
Top origin entities
invoices by op-co · affected shown darker
Summary tables
by document status — batches & invoices (Deliverable 1)
Deliverable 2
Where distribution is stuck
pipeline steps with status ≠ CMPL
Blocked steps
batches / invoices with a non-completed step · respects Report filter
Blocking state per step
NEW (pending) · EDDI (in transit) · DISC/CANC (dropped)
Top distribution routes
DIST_PROC · % of batches affected
Deliverable 3
Affected batches
click a row to drill into its EU-INV invoice detail
Batches
filter above · sort by any column · click to expand
Geography & mix
Where invoices go
EU-INV invoice level · mailing country & document type
Geography is invoice-level (EU-INV) and reflects the whole population — the Report/entity filters above apply to the batch pages, not this one. No shipment origin→destination lanes exist in the data; mailing country is the recipient country and entity the origin op-co.
Invoices by mailing country
top 20 recipient countries
Document type mix
IDR / IFR / IDCA …
Invoice status (EU-INV)
CREA / DISC / PROC / …
Top customers
by invoice count · placeholder "." excluded
Geography · flows
Invoice document map
recipient volume & billing-country → recipient flows
Colour = invoices by mailing (recipient) country. Arrows = origin op-co country → recipient country for the top cross-border flows (billing origin → where the document is sent). Click a country (either map) to isolate its flows. Values are invoice counts — the data has no monetary amount. This is invoice-document movement, not shipment lanes.
Focus country
Invoices by recipient country
choropleth · EU-INV mailing country
Cross-border invoice flows
animated top billing→recipient arrows
Reported separately
Unmatched groups
EU-INV doc-groups with no CN/INV distribution record — reported separately
Invoice status
unmatched population
Aging
days since insert · unmatched
Largest unmatched groups
top 500 by invoice count
How batches flow to a blockage
report → document status → first blocked step · width = invoices
Key findings
Recommended actions & open questions
Transparency
Data quality & coverage
Coverage
Oldest not-distributed invoices
CREA/PROC · top by age (days)
Notes
Sources: CN_Distribution.csv (credit-note batches), INV_Distribution.csv (invoice batches), EU_INV.xlsx (invoice-level detail).
Grain: the two CSVs are one row per batch (FDX_RD_DOCGRP_ID); EU-INV is one row per invoice/document.
Affected = a batch where any populated pipeline step is not CMPL.
Status codes: CMPL = complete · NEW = pending · EDDI = in transit · DISC/CANC = dropped. Exact business meaning of EDDI / WIRN / ESDI to be confirmed with the business.
Known: CN and INV reports share zero doc-groups; columns CUSTSPEC/COLUMBUS/PARAGON/ICAN/ARCH are empty; customer name "." is a placeholder; all rows are External.
Grain: the two CSVs are one row per batch (FDX_RD_DOCGRP_ID); EU-INV is one row per invoice/document.
Affected = a batch where any populated pipeline step is not CMPL.
Status codes: CMPL = complete · NEW = pending · EDDI = in transit · DISC/CANC = dropped. Exact business meaning of EDDI / WIRN / ESDI to be confirmed with the business.
Known: CN and INV reports share zero doc-groups; columns CUSTSPEC/COLUMBUS/PARAGON/ICAN/ARCH are empty; customer name "." is a placeholder; all rows are External.