K-Phi imports Sage general ledger exports directly. Whether you run Sage 50, Sage 100, Sage Intacct, or Sage X3, K-Phi reads the nominal ledger export directly. No connector, no consultants. Drop the CSV, and the platform auto-maps columns, detects your fiscal calendar, and spins up a working FP&A and treasury workspace.
There is no single "Sage" — each product line has its own export format. Sage 50 (UK/US) uses Nominal Codes and a narrow column set. Sage 100 (ex-Sage Line 100, common in France) uses French PCG headers. Sage Intacct exposes dimensions (Department, Location, Class). Sage X3 is full ERP with multi-ledger. Most FP&A tools pick one and break on the others.
K-Phi's 7-pass Smart Mapper was built specifically for this. It ships with header aliases for all four major Sage product lines in English and French, plus the PCG sign convention handling needed for Sage 100.
Drop an SAP FI GL line-item export (transaction FBL3N, FAGLL03, or an SE16 dump of BSEG/BKPF) into the upload field. Here's what gets recognized automatically:
| Sage Field (50 / 100 / Intacct / X3) | K-Phi Field |
|---|---|
| Nominal Code / Compte / Account No. | account |
| Company / Société / Entity / Legal Entity | entity |
| Transaction Date / Date écriture | doc_date |
| Posting Date / Date de saisie | post_date |
| Period No. / Période | period |
| Financial Year / Exercice | fiscal_year |
| Debit / Credit / Montant / Amount | amount_lc |
| Currency / Devise | ccy |
| Type / Journal Code / Code journal | doc_type |
| Reference / N° pièce / Document No. | doc_id |
| Department / Dimension / Section analytique | cost_center |
| Details / Libellé / Memo | memo |
FC_PROJ) seeded from your historical trendFive fields, all pre-filled from the data:
K-Phi is built for finance teams who already run Sage and just want an FP&A and treasury layer on top — without the Anaplan or Pigment rollout cost. Upload today, amend the assumptions, and your workspace is live.
Try K-Phi with your Sage export →