Use a reviewed per-resource export to supply cost data. Confirm its provider, month, currency and contents before importing; a successful parser result does not establish that the whole bill was understood.

Review the export first

Use a comma-separated file with a header row and identifiable resource and cost columns. Review which columns represent the intended cost basis. The parser recognises a defined set of header names and can fall back to partial matches; it does not understand every export format automatically.

Check a representative resource and amount, including decimal formatting. Credits, zero or negative amounts, empty resources and some non-resource placeholders are skipped. The resulting totals can therefore differ from a provider’s net invoice, taxes and account-wide charges.

Import the intended month

1. Open PD Modules → Cost & Margin → Providers.
2. Under Paste a cost export, choose Which provider is this from.
3. Set Which month it covers from the actual export period.
4. Paste the complete reviewed contents, including headers, into The export.
5. Choose Import this export, then review the imported and matched counts and provider totals.

The released importer does not enforce a single matching currency and assumes USD when the file omits currency. Use a consistent, independently verified currency basis rather than expecting an incompatible file to be rejected.

Understand a later import

Existing rows with the same provider, resource and month are updated. Resources omitted from the new file are not removed in this release, despite the panel’s replacement wording. A partial correction export can leave older rows behind.

Reconcile counts and totals before importing again. Compare any retained rows and overlapping account identifiers against the original export; do not treat repeated imports as a guaranteed monthly reset.

See the PD Cloud Cost & Margin Blesta guide for related tasks, or explore PD Cloud Cost & Margin.