Pre-built guidewire data mapping for downstream Fusion Financials: Policy → Revenue, Bill → AR, Claim Payment → AP, Premium Income → GL, Ceded Reinsurance → Ceded GL. Schedule P alignment, statutory + GAAP dual-recognition, Lloyd's syndicate overlays.
Five core data flows, dozens of edge cases. Syntra ETL ships them all as governed crosswalks with full upstream-downstream traceability preserved per record.
Guidewire InsuranceSuite holds policy, billing and claim records in a tightly-coupled data model with cross-Center foreign keys: PolicyCenter Policy → BillingCenter Bill → ClaimCenter Claim. Oracle Fusion Financials holds revenue, receivable, payable and GL records in Subledger Accounting (SLA) shape with SLA rules driving GL routing. The data mapping bridges those two worlds without losing the cross-Center linkage that auditors, regulators and reinsurers depend on. Every Fusion record carries upstream-evidence metadata — a Fusion AP claim-payment invoice always points back to the ClaimCenter Payment, the Exposure, the Claim and the originating Policy.
The five core flows are: Policy + Premium Transactions to Revenue Recognition + GL Journal; Bill + Invoice to AR Transactions; Direct/Agency Bill Payment to AR Receipt; Claim Payment (Indemnity, Expense, Recovery) to AP Invoice + paid-loss GL; Reinsurance Ceded Premium + Recovery to ceded GL + Reinsurer AP/AR. Each flow is field-mapped to the Fusion FBDI template (or REST API payload for incremental) so loads execute deterministically with zero ambiguity. Reserve changes — the heartbeat of P&C actuarial — are preserved as evidence metadata in Fusion but the authoritative reserve store remains ClaimCenter, since reserves drive the loss-development triangle that lives upstream of Fusion's general ledger.
Crucially the mapping is account-aware. Premium routing is by LOB by state by legal entity by Schedule P line. Paid-loss routing is by LOB by coverage by accident-year by state. Ceded reinsurance routing is by treaty by LOB by reinsurer. Commission routing is by producer by LOB. Without this account-aware mapping the resulting Fusion GL would be unusable for statutory reporting, GAAP financial reporting, NAIC Schedule P generation or reinsurance bordereaux — the consultant-led pattern of mapping everything to a handful of generic accounts and reconciling later is exactly the failure mode the Syntra guidewire data mapping prevents.
The exact field-by-field map across the six most common Guidewire → Fusion translation paths.
Policy.PolicyNumber → SourceTransactionNumber; Policy.LOB → RevenueAccount routing; PolicyPeriod.EffectiveDate → ContractStartDate; PolicyPeriod.ExpirationDate → ContractEndDate; PremiumAmount.Amount → LineAmount; Coverage.CoverageCode → GLSegment3.
Cr Written Premium [LOB+State+LE+SchP line] for written; Dr Unearned Premium / Cr Earned Premium for earning schedule; Dr Premium Receivable per producer-relationship; ceded leg via Cession_Reference foreign key.
Bill.BillNumber → TransactionNumber; Bill.PolicyReference → CustomerSiteAttribute; Invoice.DueDate → DueDate; InvoiceItem.Amount → LineAmount; Producer.ProducerCode → ThirdPartyPayer when AgencyBill.
Payment.PaymentNumber → InvoiceNumber; Payment.Payee → Supplier; Payment.PaymentType (Indemnity/Expense/Recovery) → InvoiceDescription + GL routing; Exposure.Coverage → GLSegment driving paid-loss GL account.
Reserve changes NOT loaded as Fusion transactions; carried as evidence metadata (ReserveAmount, ReserveDate, ReserveUser, ReserveReason) on payment Fusion records; archived in long-tail store for actuarial loss-triangle reconstruction.
CededPremium per treaty per layer → Dr Ceded Premium [Treaty+LOB], Cr Reinsurer Payable per reinsurer supplier; CededLossRecovery → Dr Reinsurance Recoverable, Cr Ceded Loss Recovery GL; bordereaux netting per quarter.
A repeatable workflow that gets crosswalks signed off by week 6 — well before extraction starts in earnest.
Discovery engine catalogues every active LOB, every active product, every state of admission, every legal entity, every active reinsurance treaty. Output: complete inventory the data mapping has to cover, no LOB missed.
Fusion chart-of-accounts extracted: segments for legal entity, account, cost-center, intercompany, LOB, state, accident-year. Schedule P line attribute confirmed for statutory roll-up. Reinsurance treaty supplier/customer setup confirmed.
Pre-built mapping templates applied — premium-to-revenue, paid-loss-to-GL, ceded-reinsurance-to-ceded-GL, commission-to-AP, claim-payment-to-AP, cash-to-AR. Account routing per LOB per state populated from chart-of-accounts.
Crosswalks reviewed by statutory accounting (Schedule P alignment), GAAP accounting (earned-premium recognition), reinsurance team (ceded routing), AR/AP leads (cash + disbursement), tax (1099 + premium tax). Each crosswalk signed.
Sample load against Fusion test pod — one month of premium, one month of paid-loss, one month of ceded. Reconciliation pack generated: Guidewire ledger vs Fusion ledger to the cent per LOB per state. Any variance triaged and crosswalk adjusted.
Final stakeholder sign-off. Crosswalk version frozen as v1 and locked for the cutover. Any post-cutover refinements happen via versioned crosswalk update with rerun-and-reconcile pattern.
A guidewire data mapping that does not preserve Schedule P traceability is unfit for purpose. Here is how Syntra handles it.
Every Fusion GL account in the premium and paid-loss flows tagged with NAIC Schedule P line code (1-17). Subledger Accounting attribute preserved so Schedule P generator rolls up Fusion data without manual reconciliation.
Every paid-loss record routed to GL with accident-year and report-year segments. Schedule P age-to-age triangle generation works off Fusion GL alone for paid-loss; reserve triangle still sources from Guidewire ClaimCenter.
Every premium and paid-loss record tagged with state-of-jurisdiction segment. State page generation per NAIC Annual Statement Page 14 works off Fusion GL without re-querying Guidewire.
Direct, assumed and ceded premium routed to separate GL account ranges. NAIC reinsurance schedules (Schedule F) and reinsurance section of Annual Statement supported from Fusion GL.
Written premium GL account separate from earned premium GL account separate from unearned reserve GL account. NAIC required disclosures supported per LOB per state per line.
Every Fusion record carries upstream-evidence metadata pointing back to Guidewire source record. Model Audit Rule control narrative supported with technical evidence per transaction.
Guidewire data mapping is the field-by-field translation layer between Guidewire InsuranceSuite's policy/billing/claim data model and Oracle Fusion Financials' GL/AP/AR/Revenue Recognition shape. Concretely it means: PolicyCenter Policy + Premium Transactions mapped to Fusion Revenue Recognition + GL Journal lines per LOB per legal entity, BillingCenter Bill + Receipt mapped to Fusion AR receipt rows, BillingCenter Disbursement mapped to Fusion AP invoice + payment, ClaimCenter Claim Payment (indemnity, expense, recovery) mapped to Fusion AP claimant invoice + paid-loss GL, and Premium Income mapped through Subledger Accounting (SLA) rules to the appropriate GL accounts. Syntra ETL ships these mappings pre-built as governed crosswalks — not as freeform field-by-field PowerPoint slides — and applies them deterministically per record with full audit trail.
PolicyCenter Policy is the parent record. Each policy has one or more PolicyPeriods, each PolicyPeriod has Coverages, each Coverage has PremiumAmount transactions (initial premium, endorsement premium, audit premium, cancellation premium). These map into Fusion as follows: Policy + PolicyPeriod become the Revenue Recognition Source Transaction with policy-period-from and policy-period-to driving the earning schedule; Coverages drive the GL account routing per LOB; PremiumAmount transactions become Revenue Recognition Lines. The earning schedule itself is calculated downstream — Fusion's Revenue Recognition module spreads written premium across the policy period straight-line by default, with pro-rata month-end recognition. Syntra ETL preserves the Guidewire policy hierarchy (Policy → PolicyPeriod → Coverage → PremiumAmount) as evidence metadata on each Fusion Revenue Recognition record so auditors can trace any earned-premium amount back to the originating PolicyCenter transaction.
BillingCenter handles the receivable side. Each Bill in BillingCenter has Invoices, each Invoice has InvoiceItems linked back to PolicyPeriod and to a Producer (agent/broker), and each receipt of payment is a DirectBillPayment or AgencyBillPayment record. The Fusion data mapping is: Bill → AR Transaction Header; InvoiceItem → AR Transaction Line; DirectBillPayment → AR Receipt; AgencyBillPayment → AR Receipt with producer-as-third-party-payer metadata; commission liability → AP Invoice payable to producer supplier in Fusion AP. Cash application in Fusion AR is driven by the BillingCenter cash-application logic — Syntra ETL preserves the application chain so a Fusion AR receipt always points back to the BillingCenter receipt that paid which invoice that billed which policy. End-to-end traceability.
ClaimCenter Claim Payment is the most complex mapping. Each Claim has Exposures (one per coverage triggered), each Exposure has Reserves (case + IBNR), and each Payment is tied to an Exposure and a payment-type (Indemnity, Expense — split into ALAE/ULAE, Recovery for subrogation/salvage). The mapping into Fusion: Claim Payment header → AP Invoice header payable to claimant supplier (or vendor supplier for ALAE); Payment lines → AP Invoice lines; GL accounting via SLA → paid-loss GL account by LOB by coverage by accident-year by state. Reserve changes are NOT loaded as financial transactions in Fusion — they are carried as evidence metadata since reserves drive the actuarial loss-development triangle that lives upstream of Fusion. Recovery payments are routed to Recovery GL accounts (negative paid-loss). Subrogation receipts flow back through BillingCenter as cash and reconcile to the Recovery GL.
Premium Income in Guidewire is computed at PolicyCenter level (written premium per policy per LOB per state per accident-year) and recognised over the policy period as earned premium. The guidewire data mapping into Fusion GL has two layers: (1) Written Premium hits the GL on the policy effective date — Cr Written Premium (specific GL account per LOB per state per legal entity), Dr Premium Receivable; (2) Earned Premium is recognised per period — Dr Unearned Premium Reserve, Cr Earned Premium. Both flows are driven by Fusion's Revenue Recognition module with Guidewire as the source-transaction supplier. Direct-written premium routes to direct GL accounts; assumed premium (from reinsurance assumed business) routes to assumed GL accounts. Ceded premium (premium ceded to reinsurers) routes to ceded GL accounts and ceded-premium-payable in AP.
NAIC Schedule P organises paid-loss, incurred-loss and case-reserve data by accident-year and report-year per Annual Statement line of business (Schedule P Part 1 has 17 lines: Homeowners, Private Auto Liability, Private Auto Physical Damage, Commercial Auto Liability, Workers Compensation, Commercial Multi-Peril, Medical Professional Liability, Special Liability, Other Liability — Occurrence, Other Liability — Claims-Made, Special Property, Auto Physical Damage Commercial, Fidelity/Surety, Other, International, Reinsurance — Non-Proportional Property, Reinsurance — Non-Proportional Liability, Reinsurance — Non-Proportional Financial Lines, Products Liability — Occurrence, Products Liability — Claims-Made, Warranty). The guidewire data mapping includes a Schedule P line code per LOB per coverage per Fusion GL account, preserved as Subledger Accounting attribute, so the Schedule P generator can roll up Fusion GL data without manual reconciliation back to Guidewire. Reserves remain sourced from Guidewire (not Fusion) for Schedule P.
Ceded reinsurance flows through Guidewire with a specific reinsurance ceded module — each policy that triggers a treaty cession gets a Ceded Premium amount calculated per layer, each claim payment that triggers treaty recovery gets a Ceded Loss Recovery calculated per layer. The data mapping into Fusion: Ceded Premium → Dr Ceded Premium GL (per treaty per LOB), Cr Reinsurer Payable in AP per reinsurer supplier; Ceded Loss Recovery → Dr Reinsurance Recoverable in AR per reinsurer customer, Cr Ceded Loss Recovery GL (per treaty per LOB); Bordereaux settlements net ceded premium against ceded recovery per quarter and settle through AR/AP between reinsurer and cedant. Every cession is cross-referenced to the source policy and source claim payment so reinsurance audits can trace any Fusion GL line back to the originating risk.
Yes — the base mapping covers a US P&C carrier. For London-market specialty insurers and Lloyd's syndicates the mapping adds Underwriting Year accounting (instead of accident-year), three-year accounting closure cycles, Lloyd's Premium Income Monitoring (PIM) tagging per syndicate, Lloyd's Coverholder reporting (binding-authority business through delegated authorities), Solvency II SCR data points on each premium and loss record, and specific GL routing for Lloyd's Central Fund contributions. Syntra ETL has Lloyd's-flavour mapping templates that overlay on top of the standard Guidewire mapping. For Bermuda captives and Cayman captives, parent-company-allocation GL routing and ISO XBRL tagging is added. All variants share the same crosswalk engine — only the templated rules differ.
Book a 30-minute discovery call. We will walk through your LOB inventory, your Fusion chart-of-accounts, your Schedule P routing requirements and your reinsurance treaty footprint — and give you a concrete data mapping scope and timeline before the call ends.