Cases / Commercial & contracts
Commercial & contracts

Send a bill to Spain in FIEBDC-3

Export a priced bill to FIEBDC-3, the budget format the Spanish and Latin American market exchanges in, so it opens as a real budget in a desktop estimating tool and comes back through your own reader unchanged.

4 steps11 minCost consultancy / QS practiceGeneral contractorSpecialist subcontractor

How it works, step by step

4 steps across the platform - what you do at each one, and why it matters.

1

Get the bill ready to travel

BOQ

Check the bill has the shape BC3 expects before you export anything: a chapter for each section, an item for each position, and a code, a unit, a quantity and a unit rate on every line. Long descriptions travel too, so read the ones you would rather a client did not see.

Why: BC3 carries a hierarchy, so a bill with orphaned positions or two items sharing a code arrives at the other end as a budget nobody can navigate. Sorting the tree out here takes minutes. Sorting it out after someone has started pricing in their own software is no longer your decision to make.

InPriced billChapter structureOutClean chapter and item treeEvery position coded
2

Export to FIEBDC-3

BOQ

Export the bill to FIEBDC-3. The file carries the chapters and items with their codes, units, quantities, unit rates and long texts, which is what a Spanish desktop estimating tool needs to open it as a working budget instead of a list of numbers.

Why: BC3 is what that market actually exchanges budgets in, and for Spanish public work it is not optional. Sending a spreadsheet instead means somebody at the other end retypes your bill, and a retyped bill of four hundred positions always loses a few.

InStructured priced billFIEBDC-3 exportOutBC3 budget fileHierarchy, rates and texts
3

Check the charset in the header

BOQ

Open the file and read the charset the header declares. It is written Windows-1252 by default, which is what the desktop tools in that market expect, and it switches to UTF-8 only when a character in your texts cannot be represented. Either way the header states which one was used.

Why: A mis-declared charset is the classic BC3 failure. The file opens, the numbers are all correct, and every accented character in the descriptions comes out as rubbish. It gets spotted late, usually by the client reading your descriptions, and it makes an otherwise careful submission look sloppy.

InBC3 filePosition textsOutCharset named in the headerText that survives the trip
4

Prove the round trip

BOQ

Read the file you have just written straight back in through the BC3 importer and compare it against what you exported. Codes, chapters, quantities, units, rates and long texts should all come back the same.

Why: An export nobody has ever read back is a guess. Putting it through your own reader takes a minute and is the difference between believing the file is sound and knowing it, which matters most on the submission where you do not get a second go.

InExported BC3 fileBC3 importerOutRe-imported billConfirmed match
Modules

Modules in this playbook

BOQ

1 / 184 platform modules

More in Commercial & contracts

Commercial & contracts

Run a subcontractor package

Award a trade package to a subcontractor, place it on a subcontract with a schedule of valu…

3 steps11 minOpen