Extract Mail Boxes Etc Invoices to Excel: Pan-EU Workflow

Extract Mail Boxes Etc invoices from multiple EU franchisees into one Excel sheet — multi-country, multi-language, with per-consignment cost analysis.

Published
Updated
Reading Time
20 min
Topics:
Industry GuidesLogisticsEUMail Boxes Etcparcel shippingecommerce shipping reconciliation

Mail Boxes Etc invoices arrive separately from each country's MBE franchisee, each on its own template, in its own language, with its own VAT registration. To extract Mail Boxes Etc invoices to Excel and consolidate them into a single sheet, pull per-line tracking number, recipient, MBE service code (Express, Mondiale, Easy Send), base cost, surcharges, and VAT — then join on tracking number to the underlying order data for cost-per-consignment analysis.

The reason your stack of MBE invoices looks the way it looks is structural, not accidental. MBE is a brand network of independent franchise centres, not a single carrier and not a single billing entity. According to the platform's owner, the network includes 3,200+ Business Solutions Centers across 57 countries, with locations operated by independent master licensees and franchisees rather than a single carrier. Each centre runs as its own legal entity, with its own VAT registration. Templates are customised per franchisee — built around MBE's brand assets but laid out, labelled, and rendered locally, with surcharge lines in the centre's working language.

That franchise-consolidator pattern is what produces the operational reality on your desk. Five MBE invoices from five different EU franchisees mean five VAT numbers, five template variants, and five language renderings of the same underlying surcharge categories. The MBE brand surface conceals this; the operational reality is per-franchisee, and the stack stops being annoyingly inconsistent paperwork once you read it as the predictable output of a specific business model.


The MBE Service-Code Taxonomy and the Hidden Carrier

The service-code line on an MBE invoice tells you which MBE-internal tier the consignment shipped under. It does not tell you which underlying carrier carried it. Reading those lines accurately, and knowing where that reading stops, is the first practical skill the MBE-customer workflow demands.

The set you'll see across most centres is small. MBE Express is the international express tier — fastest international transit, time-definite delivery, used for cross-border shipments where the customer paid for speed. MBE Mondiale is the international economy tier — slower international transit, lower cost, the workhorse for non-urgent intra-EU and cross-border consignments. MBE Easy Send covers domestic and intra-EU standard parcel shipments — most of the typical SME ecom volume sits here. MBE Boxes & Materials is not a shipping service at all — it's the packaging line, billed when the franchisee supplied boxes, padded envelopes, mailers, or fillers as part of fulfilling the consignment. MBE Insurance is declared-value coverage — billed per consignment when the SME opted into protection above MBE's standard liability.

Asked which carriers actually move the consignments, the honest answer is "it depends on the franchisee, and the invoice doesn't say." The MBE invoice line names the MBE tier and the consignment cost; the franchisee's underlying carrier mix is a commercial arrangement the SME usually cannot see from the document alone. Anything below is inference, not guarantee. MBE Express vs MBE Mondiale service codes typically map to international express and international economy products from DHL, UPS, FedEx, or TNT — MBE Express is most often DHL Express international or UPS, sometimes TNT or FedEx Priority depending on the local centre's contract; MBE Mondiale tends to ride DHL Economy, FedEx Economy, or a comparable international economy product. MBE Easy Send moves on whichever domestic carrier the franchisee contracts with — frequently the national post (Poste Italiane, Deutsche Post DHL, Correos, CTT, La Poste), sometimes a regional courier.

That opacity is the structural fact behind the term MBE invoice carrier passthrough. The franchise centre pays the underlying carrier and bills the SME a consolidated MBE-tier rate, sometimes with a small set of MBE-aggregated surcharge lines on top. Either way, the underlying carrier's surcharge schedule — fuel index for the period, residential surcharge, peak-season uplift, dimensional-weight calculation — does not pass through to the MBE invoice line by line. The franchisee absorbs that complexity into its MBE-tier pricing. This is structurally different from a carrier-direct invoice, where each surcharge category appears on its own line and can be checked against the carrier's published schedule.

The practical consequence sets the boundary of what an MBE invoice can answer. If the question is "audit my carrier surcharges against the carrier's published rates," MBE is the wrong document type to start from — that's the carrier-direct parcel invoice audit for UPS, FedEx, and DHL workflow, applicable to operators billed directly by the carrier with the full surcharge schedule on the invoice. What MBE invoices do support, and support cleanly, is consignment-level cost analysis at MBE's own pricing — what each consignment cost the SME, broken out by service tier, country of issuing centre, and the surcharge lines the franchisee chose to expose. The rest of this article builds that workflow.


Template, Language, and Layout Variation Across Franchisees

The bottleneck that makes MBE franchise invoice template variation a workflow problem rather than a paperwork annoyance is structural, and it shows up the moment a single SME ships through more than one MBE centre.

Per-franchisee template variation is the first layer. Even within a single country, individual MBE centres customise their invoice layouts. Centro logo placement, header structure, the column order in the line-item table, the position of the VAT block, the labelling of footer fields, whether tracking numbers sit in their own column or are appended to the recipient field — each centre's invoice carries the MBE brand without inheriting a uniform template. A template-based extractor configured against MBE Italia centre A in February breaks when MBE Italia centre B's invoice arrives in March with the line-item columns in a different order. Configure a new template, ship the next month, hit the next centre, configure another template. The work compounds rather than amortising.

The language layer stacks on top. An Italian fattura lists fuel surcharge as Carburante. A German Rechnung labels the same line Treibstoff. A Spanish factura uses Combustible, a Portuguese fatura uses Combustível, a French facture uses Carburant. Toll surcharges read Pedaggio in Italian, Maut in German, Peaje in Spanish, Péage in French. VAT renders as IVA, MwSt, IVA, IVA, TVA in those same languages, and the rate sitting next to the label is the issuing country's standard rate, not the SME's home rate. Each invoice arrives in the working language of the centre that issued it, regardless of the language the SME's finance team works in.

The extraction approach that survives this is to invert the problem. Instead of teaching an extractor about each layout and each language, name the fields the SME wants once — consignment ID, tracking number, MBE service code, recipient, country of issuing centre, base cost, surcharges, VAT amount, VAT jurisdiction, total — and let the extraction engine handle layout and language as it reads. The prompt is the configuration. It does not need to know in advance whether the next document is a Bavarian Rechnung or a Lisbon fatura; it needs to know which fields are wanted in the output, and the engine reads them out of whatever layout and whichever language the invoice was issued in. One prompt, one schema, every centre.

This is the step where AI invoice extraction across MBE franchise templates and languages earns its place in the workflow. The product runs as a single prompt field over a file-upload area, with no templates to configure and no per-language localisation work for the SME to do. A finance lead writes one prompt that names the columns the consolidation needs, uploads the month's six MBE PDFs together, and receives one Excel file with every consignment normalised into the same schema. The German Rechnung's Treibstoff line and the Italian fattura's Carburante line both land in the Fuel Surcharge column. The same prompt produces the same structured result whether the batch is six invoices this month or sixty next quarter, which is the bar that pan-EU ecommerce shipping invoice consolidation actually has to meet: consistency across documents, not best-effort handling of one PDF at a time.

Tracking Number and Recipient Name as Your Join Keys

Two fields on every consignment line of an MBE invoice do the heavy lifting for downstream analysis: the tracking number and the recipient name. Both appear on every consignment row across every franchisee template the SME receives, and both extract cleanly into the consolidated spreadsheet — which means both are available as the join keys back to the SME's order data.

The tracking number per consignment is the cleanest path. When a consignment ships, the franchisee's underlying carrier issues a tracking string and the franchisee writes it onto the invoice line for that consignment. On the SME's side, that same tracking number lands in the order management system at fulfilment time — typically through the franchisee's shipping label, the SME's MBE-portal integration, or an emailed shipping confirmation that triggers the shop's tracking-number update. Order ID and tracking number live together in the order data. Joining the extracted MBE invoice on tracking number returns one shipping cost per order, exactly. There's no fuzzy matching, no date-window heuristic, no reconciliation tolerance to negotiate.

The fallback applies when tracking number didn't make it back to the order record — which happens, particularly with manual fulfilment where the franchisee created the consignment in their own system without round-tripping the tracking string to the SME's shop. In that case, recipient name plus shipment date is the soft join: not as strong, because two different orders can ship to the same customer in the same month, but workable when the date window is tight enough to disambiguate. Recipient name on its own isn't enough for repeat customers; recipient name plus a two-or-three-day date window usually is. The honest framing is that the tracking-number join is the design target and the recipient-name fallback is the rescue path, not a substitute.

Once the join lands, every column the extraction produced attaches to the order record. The MBE service code attaches, so the SME can see which orders shipped via Express, which via Mondiale, which via Easy Send. The country of the issuing centre attaches, so per-country shipping cost falls out of a pivot. Base cost and surcharge breakdown attach, so the SME can see whether the surcharge ratio is rising over time on a particular country's lane. The result is one row per order carrying not just total shipping cost but the structural detail that turns shipping cost into actionable cost-per-consignment analysis — which lane is expensive, which service tier is dragging margin, which country's MBE pricing has drifted since last quarter.


How MBE Handles Surcharges — Two Patterns, Two Workflows

MBE franchisees consolidate carrier surcharges into one of two patterns on their invoices, and a single SME using more than one centre often sees both. Recognising which pattern a given invoice uses is quick once you know what to look for; the schema for the consolidated spreadsheet has to accommodate both.

The first pattern is the flat MBE service rate. The franchisee bills a single per-consignment amount and that amount is everything — the underlying carrier's base shipping, the fuel surcharge for the period, the toll component if applicable, any residential surcharge, packaging if it was bundled into the service rate. There are no surcharge lines on the invoice to extract. The line you read is the line you book. For cost analysis, the consignment row carries one number under Total and the surcharge columns sit empty. Cleanest possible input for per-consignment cost analysis. The trade-off is that the SME has no leverage to push back on a particular surcharge category — there is no fuel-surcharge line to see drift on, because the franchisee absorbed the surcharge into the service rate before issuing the invoice.

The second pattern is the aggregated surcharge breakdown. The franchisee bills a base service charge per consignment plus a small set of additional lines on the invoice — typically a fuel surcharge, sometimes a toll surcharge for routes that crossed pay-per-use roads, sometimes a declared-value insurance line, occasionally a residential or out-of-area surcharge. The labels render in the issuing centre's language: Carburante / Treibstoff / Combustible / Combustível / Carburant for fuel, Pedaggio / Maut / Peaje / Péage for toll, Assicurazione / Versicherung / Seguro for insurance. These lines are MBE-internal aggregations of what the franchisee paid the underlying carrier — they are not the underlying carrier's surcharge schedule reproduced on the MBE invoice. The aggregation level is one step removed from the carrier.

What each pattern permits and prevents follows from that structural difference. Flat-rate franchisees give the SME a clean per-consignment number for cost-per-order P&L but no granular visibility into where surcharge inflation is happening. Itemised franchisees let the SME track fuel-surcharge ratios month-on-month, isolate toll exposure to particular destinations, and see whether insurance is being applied to consignments that didn't request it — but the visibility is into MBE's aggregation of carrier surcharges, not the carrier's own schedule. Neither pattern supports a carrier-audit workflow; both support consignment-level cost analysis at MBE pricing.

Designing the consolidated spreadsheet schema for both patterns at once is straightforward when you accept that some cells will sit empty. Columns for Base Cost, Fuel Surcharge, Toll Surcharge, Insurance, Other Surcharges, and Total cover the itemised pattern; flat-rate consignments fill only Total, leaving the surcharge columns blank. The Total column is the source of truth for cost-per-consignment analysis across both patterns and is the column the order-data join produces shipping cost from. The surcharge columns become useful where they're populated and stay out of the way where they're not.


Multi-Country VAT on the Receiving Side

A pan-EU SME using MBE centres in multiple member states receives Mail Boxes Etc invoice multi-country VAT in mixed jurisdictions, every month. A German-registered SME shipping through MBE centres in DE, IT, ES, FR, PT, AT will see Italian IVA at 22%, German MwSt at 19%, Spanish IVA at 21%, French TVA at 20%, Portuguese IVA at 23%, and Austrian MwSt at 20% across that month's stack. Each invoice carries the issuing franchisee's VAT number and the issuing country's VAT rate. The accountant's treatment of those amounts depends on the per-country relationship between the SME and the issuing franchisee — a treatment the consolidated spreadsheet has to make legible without prejudging.

For the receiving SME, MBE invoices issued by franchisees in countries other than the SME's home country sit in the broader category of intra-EU acquisition of services. The standard treatment, where the SME is VAT-registered and the franchisee is a B2B supplier, is the home-country reverse-charge mechanism: the SME accounts for the VAT in its home country, the franchisee invoices net of VAT (or with the originating-country VAT for the SME's accountant to handle on the appropriate intra-EU schedule). The local-country MBE invoice — the one issued by a franchisee in the SME's own home country — typically reads as a domestic supply with home-country VAT charged in the normal way. None of this is tax advice; the SME's accountant owns the actual treatment per row, working from EU VAT directives that the practical OSS / IOSS framing rests on top of.

The job of the consolidated spreadsheet is to carry enough VAT detail per row that the accountant can apply correct treatment without losing per-invoice attribution. Four columns earn their place: VAT Amount, VAT Rate, VAT Jurisdiction (the issuing country's two-letter code — IT, DE, ES, FR, PT, AT, BE, NL, IE, and so on), and Issuing Centre VAT Number (the franchisee's full VAT registration as printed on the invoice). With those four columns populated per consignment, the accountant has every input needed to slot each row into the correct VAT treatment — domestic, intra-EU acquisition, or where exceptions apply.

One pointer keeps OSS and IOSS in the right scope. SMEs using OSS or IOSS for outbound B2C ecommerce — the schemes that simplify reporting on what the SME charges its end customers across the EU — still handle inbound MBE invoices as standard intra-EU acquisition under their home-country VAT registration. OSS and IOSS govern what the seller charges its buyers; they do not change how the seller receives invoices from its suppliers. The outbound side has its own control — reconciling IOSS-collected VAT against the carrier's customs lines so cross-border parcels aren't charged VAT twice — but that runs on DHL, UPS, and FedEx invoices rather than on MBE franchise invoices. The MBE franchisees are suppliers to the SME, not customers, so the inbound MBE VAT logic runs on the standard rules even when the SME's outbound flow is under OSS / IOSS.


A Pan-EU Worked Example — Six Invoices, Six Countries, One Spreadsheet

Take a German-headquartered ecommerce brand shipping through MBE centres in Munich (DE), Milan (IT), Madrid (ES), Paris (FR), Lisbon (PT), and Vienna (AT). One month, the brand receives six MBE invoices — one per country franchisee — covering roughly 240 consignments in total. The mix is what a typical pan-EU ecom shipper sees: a small share via MBE Express to non-EU customers in the UK, US, Switzerland, and beyond; another share via MBE Mondiale for international economy; the bulk via MBE Easy Send for domestic and intra-EU standard parcel.

The consolidated spreadsheet schema collapses those 240 rows across six invoices into one sheet. The columns, in order, are: Consignment ID (the SME's own internal reference, joined back from the order data), Tracking Number (the carrier tracking string per consignment), MBE Service Code (Express, Mondiale, Easy Send, or other), Recipient Name (the customer name as the franchisee recorded it), Country of Issuing Centre (the two-letter code of the franchisee's country), Issuing Centre VAT Number (the franchisee's VAT registration as printed), Service Date (when the consignment shipped), Base Cost, Fuel Surcharge, Toll Surcharge, Insurance, Other Surcharges, VAT Amount, VAT Rate, VAT Jurisdiction, and Total. The schema is wide enough to carry both surcharge patterns and narrow enough that a finance-literate reader can reproduce it in any spreadsheet tool.

The extraction step is where the six invoices become one sheet. One prompt names the columns. The six PDFs go up as a single batch. The output is one Excel file with all 240 consignments normalised into the schema above — German Rechnung surcharge labels, Italian fattura IVA lines, French facture TVA lines, Portuguese fatura surcharges, Spanish factura totals, Austrian Rechnung lines, all routed into the same columns. The Italian Carburante and the German Treibstoff both land under Fuel Surcharge. The IVA at 22% from Milan and the TVA at 20% from Paris both populate VAT Amount and VAT Rate, with VAT Jurisdiction differentiating them as IT and FR respectively.

A working prompt for this consolidation reads roughly as follows:

I am consolidating monthly Mail Boxes Etc invoices from franchisees across multiple EU countries into a single per-consignment spreadsheet. Each invoice arrives in the issuing centre's local language (Italian, German, Spanish, Portuguese, French) and has its own template layout. Extract one row per consignment with these columns: Consignment ID (use the franchisee's reference if present, otherwise leave blank), Tracking Number, MBE Service Code (MBE Express, MBE Mondiale, MBE Easy Send, MBE Boxes & Materials, MBE Insurance, or other if listed), Recipient Name, Country of Issuing Centre (two-letter code based on the franchisee's address), Issuing Centre VAT Number (full VAT registration as printed), Service Date (YYYY-MM-DD), Base Cost, Fuel Surcharge, Toll Surcharge, Insurance, Other Surcharges, VAT Amount, VAT Rate (as a percentage), VAT Jurisdiction (two-letter country code matching the VAT regime applied), and Total. For invoices using a flat MBE service rate with no separate surcharge lines, populate Total only and leave the surcharge columns blank. For invoices with itemised surcharge lines, map fuel-surcharge labels (Carburante, Treibstoff, Combustible, Combustível, Carburant) into Fuel Surcharge and toll-surcharge labels (Pedaggio, Maut, Peaje, Péage) into Toll Surcharge regardless of which language the line is in. Skip any pages that are summary or cover sheets.

That prompt produces the consolidated sheet directly. From there, the join on Tracking Number against the brand's order data attaches Consignment ID and turns the consolidated invoice into a per-order shipping cost dataset for all 240 consignments. Cost-per-country, cost-per-service-tier, and cost-per-SKU rollups are pivot-table work the SME runs themselves in Excel, with the consolidated sheet as the source. At ~240 consignments and six PDFs a month, the volumes sit comfortably inside MBE's typical SME range, and the extraction batch is small enough that the work is a once-a-month operational task rather than a project.


What This Workflow Isn't

The franchise-consolidator angle defines what this workflow handles and, equally usefully, what it doesn't. Three adjacent workflows look superficially similar from a distance and are operationally distinct up close.

This is not a carrier-audit workflow. The whole point of the franchise-consolidator pattern is that the underlying carrier sits behind the MBE franchisee — the carrier's surcharge schedule does not pass through to the MBE invoice line by line, and the franchisee absorbs the carrier-side complexity into MBE-tier pricing or a small set of MBE-aggregated surcharge lines. SMEs whose actual question is "audit my UPS, FedEx, or DHL surcharges against the carrier's published rate card" need the carrier-direct invoice that comes from billing the carrier directly, not an MBE invoice. What this article covers is per-consignment cost analysis at MBE pricing, with full visibility into MBE service tier, country of issuing centre, and whichever surcharge breakdown the franchisee chose to expose — not surcharge audit.

This is not a software-consolidator workflow. Sendcloud and similar platforms consolidate multiple carriers behind one software layer, one API integration, and one billing relationship — the resulting invoice has a different shape, the data join runs through the platform's order-and-shipment IDs rather than per-franchisee tracking numbers, and the audit angle is meaningfully different because the consolidator passes carrier surcharges through rather than absorbing them. SMEs running on a software consolidator will recognise more of their workflow in Sendcloud's software-consolidator invoice reconciliation than in the franchise-retail-consolidator pattern this article walks. Brands comparing Huboo, Bleckmann, Bigblue, and other fulfilment partners are closer to a multi-3PL invoice consolidation across Europe workflow than to MBE franchise-issued parcel invoices. Operators dealing with weekly recurring uniform-rental billing across many sites — Cintas, UniFirst, Vestis, Alsco, Aramark — sit closer to a per-location uniform-rental invoice extraction for multi-site facilities AP workflow, which shares the multi-location consolidation shape but runs on weekly service-route invoices rather than franchise-issued parcel ones. What MBE-customer extraction handles is the multi-country, multi-language, multi-template franchise-issued invoice — a document type the software-consolidator playbook simply doesn't apply to.

This is not the returns side of cost-per-order analysis. The workflow above turns outbound MBE shipping invoices into a per-consignment spreadsheet that joins to outbound order data — fulfilment cost on the way out. Returns through MBE (where the franchisee handles return logistics) carry their own consignment lines and their own join paths, and the full cost-per-returned-order ecommerce reconciliation calculation pulls together outbound shipping cost (covered here), returns shipping cost, the refund itself, and downstream disposition costs like restocking or write-off. The MBE outbound workflow above is one input into that broader returns-side calculation, not a substitute for it.

Extract invoice data to Excel with natural language prompts

Upload your invoices, describe what you need in plain language, and download clean, structured spreadsheets. No templates, no complex configuration.

Exceptional accuracy on financial documents
1–8 seconds per page with parallel processing
50 free pages every month — no subscription
Any document layout, language, or scan quality
Native Excel types — numbers, dates, currencies
Files encrypted and auto-deleted within 24 hours
Continue Reading