BC3 import errors and integration problems

Patterns found in real construction workflows.

• Import flattens chapters or drops quantities
• BC3 goes in but cannot come out
• The accepted estimate overwrites the original bid
• Purchases have no work-item link
• Delivery notes arrive through messaging
• Labour hours are recorded only at project level
• Valuations require spreadsheet copying
• Variations mix with the contract
• Invoices are rebuilt from scratch
• The margin is only known at project close

When estimating software, spreadsheets, ERP, accounting, email and messages hold different versions, each project close requires manual reconciliation. Multiple tools are workable; missing shared identifiers and states are not.

First stabilise a validated BC3 and an unambiguous budget version. Then connect procurement and actual cost. Finally automate valuations, invoices and margin reporting.

Keep the original and record the exact error. Confirm that it is an exported BC3 file, not a renamed document. Check the version and encoding, validate where possible and try a compatible export. Avoid changing encoding blindly on the only original.

Compare the same scope: estimate, chapter or item. Locate the first difference and check quantities, decimals and calculation rules. For missing breakdowns or measurements, establish whether they were in the file and whether the importer supports them. A matching total alone is insufficient validation.