Pre-built guidewire load automation for Fusion Financials. FBDI AR for BillingCenter premium bills, FBDI AP for ClaimCenter claim payments + commission, FBDI Journal Import for premium + paid-loss GL, ESS tracking, error recovery, four configurable cadences.
Fusion's load layer is multiple FBDI templates plus REST API endpoints, plus ESS scheduler orchestration, plus reconciliation feedback loops. Doing this manually for P&C-scale volume is infeasible. Doing it through hand-coded scripts is a 6-month build. Syntra ETL ships it pre-built.
A mid-sized P&C carrier writes 500K+ premium transactions per month, processes 100K+ claim payments per month, runs 50K+ cash receipts per month and dispatches 10K+ commission disbursements per month. Every one of these has to land in Oracle Fusion Financials with correct account routing, correct supplier or customer setup, correct period attribution, correct evidence metadata and correct reconciliation. Manual load is infeasible. Hand-coded automation typically takes a consultant team 4-6 months to build and then breaks every quarterly Fusion release because Oracle changes FBDI templates or ESS interfaces. Syntra ETL's guidewire load automation ships pre-built against the current Fusion 26x release with automatic upgrade tracking — release upgrades take days, not months.
The automation surface area covers four Fusion modules. Accounts Receivable: BillingCenter invoices loaded via AutoInvoice Transaction Import FBDI; BillingCenter receipts loaded via Receipt Import FBDI with AutoMatch cash application; AR adjustments handled via dedicated FBDI template. Accounts Payable: ClaimCenter claim payments loaded via AP Invoice Import FBDI; BillingCenter commission disbursements loaded same way; new claimant + producer suppliers loaded via Supplier Import FBDI with dependency ordering. General Ledger: written-premium and paid-loss postings loaded via Journal Import FBDI with full segment values. Revenue Recognition: PolicyCenter policies loaded as Source Transactions for the Revenue Recognition module to run earning schedules.
ESS tracking is the operational backbone. Every FBDI submission generates an ESS request with a lifecycle (Wait → Ready → Running → Succeeded / Failed / Warning) and Syntra ETL tracks the lifecycle of every request automatically — polling every 30 seconds, logging each event, capturing output logs on completion, extracting failed-row diagnostics, orchestrating retry for transient failures. The operator dashboard provides single-pane-of-glass visibility across all in-flight ESS jobs per close cycle — no logging into Fusion Scheduled Processes to chase a single job, no manual coordination of dependent jobs. This is the difference between operations being a 4-hour daily check and operations being a 30-second glance at a dashboard.
What Syntra ETL ships out of the box. No bespoke ESS coding, no quarterly Fusion-upgrade rebuild, no manual operator coordination.
AutoInvoice + Receipt + Apply Receipts for AR; AP Invoice Import + Supplier Import for AP; Journal Import for GL — all orchestrated with dependency ordering automatically (suppliers before AP invoices, customers before AR receipts).
Real-time / near-real-time, hourly batch, end-of-day batch, end-of-cycle batch — configurable per data domain (claim payments hourly, ceded reinsurance end-of-quarter, etc.) through admin console.
Every ESS request polled every 30 seconds; lifecycle event logged with timestamp; output log captured; failed-row diagnostics extracted; single-pane-of-glass operator dashboard across all in-flight jobs.
Pre-load schema validation locally; ESS-layer auto-retry for transient failures with exponential backoff; post-load reconciliation recovery with field-level diagnostics and idempotent replay.
Multiple Guidewire source profiles in parallel — CDA + Cloud API for GWCP, JDBC read-replica for on-prem — feeding unified crosswalk engine and identical Fusion FBDI output. Single operator dashboard.
FBDI templates and REST endpoints tracked against current Fusion 26x release with automatic upgrade tracking. Release upgrades take days, not months — no hand-coded ESS rebuild.
The same six stages run for every batch — hourly, end-of-day, end-of-cycle. Operators see status at each stage on the dashboard.
CDA incremental Parquet exports + Cloud API modified-since deltas + on-prem JDBC change-data-capture (if hybrid) — all batched together by close period and target Fusion module.
Pre-built crosswalk engine applies premium-to-revenue, paid-loss-to-GL, ceded-reinsurance-to-ceded-GL, commission-to-AP, claim-payment-to-AP, cash-to-AR rules. Output: Fusion-ready FBDI payloads per template.
FBDI payloads validated against current Fusion 26x release schema locally. Any schema errors caught with row-level diagnostics and surfaced before submission. No 4-hour ESS jobs failing on row 200,000.
ZIP FBDI file uploaded to Fusion UCM via REST; Load Interface File for Import ESS job submitted; Import job submitted with parent-child dependency; ESS request IDs captured in operator dashboard.
Each ESS request polled every 30 seconds; lifecycle event logged; output log captured on completion; failed-row diagnostics extracted; transient failures auto-retried; permanent failures escalated.
Row-level reconciliation between Guidewire source and Fusion target per batch; counts + sums + hash signatures compared per LOB per state per period; reconciliation pack updated and any variance surfaced to operator dashboard.
Different data domains want different cadences. Syntra ETL supports per-domain configuration so each cadence matches the business need.
ClaimCenter claim payments loaded hourly via FBDI AP Invoice Import. Supports same-day cash position visibility for treasury and same-day reserve-release recognition for actuarial.
PolicyCenter premium transactions loaded hourly via FBDI Journal Import. Supports intraday revenue-recognition tracking and real-time written-premium dashboards.
BillingCenter receipts loaded hourly via FBDI Receipt Import with AutoMatch. Supports intraday cash position and same-day producer-commission accruals.
New claimant suppliers and new producer suppliers loaded via Supplier Import on-demand whenever ClaimCenter or BillingCenter creates a new payee. Dependency ordering ensures AP invoices follow suppliers.
Ceded premium and ceded recovery loaded end-of-quarter aligned with reinsurance bordereaux cycle. Supports clean treaty settlement with broker.
Manual GL adjustments (write-offs, accruals, statutory adjustments) loaded end-of-period after close-readiness signoff. Supports clean period-close attribution.
Guidewire load automation is the engine that takes Guidewire data extracted via Cloud Data Access (CDA), Cloud APIs and on-prem JDBC and pushes it into Oracle Fusion Financials' load layer — FBDI for bulk, REST API for incremental — without manual intervention. For a P&C insurer the load surface area is substantial: FBDI Receipt Import + FBDI AR Transaction Import for BillingCenter cash; FBDI AP Invoice Import for ClaimCenter claim payments and BillingCenter commission disbursements; FBDI Journal Import for written-premium and earned-premium GL postings from PolicyCenter; FBDI Supplier Import for new claimant and producer suppliers; ESS job tracking for every submission. Syntra ETL's guidewire load automation orchestrates all of this on a configurable cadence (real-time, hourly, end-of-day, end-of-cycle) with full ESS job lifecycle tracking and row-level reconciliation feedback.
BillingCenter is the source of all premium bills and cash receipts in a P&C carrier. Premium-bill FBDI for AR uses two FBDI templates: AutoInvoice Transaction Import (load BillingCenter invoices as AR transactions) and Receipt Import (load BillingCenter receipts as AR receipts with cash application). The automation flow: extract BillingCenter invoices and receipts via CDA every hour; transform via crosswalk to populate AutoInvoice + Receipt FBDI templates; ZIP and upload to UCM via Fusion REST; submit Load Interface File for Import via ESS; submit AutoInvoice Import via ESS; submit Apply Receipts using AutoMatch via ESS; monitor ESS job status; reconcile per producer per period. The automation handles the seven-step ESS dance without manual operator intervention and the validation pack signs off the cash-application chain per close cycle.
ClaimCenter claim payments — Indemnity, Expense (ALAE/ULAE), Recovery — are the largest AP volume for a P&C carrier. AP Invoice Import is the FBDI template used; supplier setup happens via Supplier Import for any new claimant payee not already in Fusion. The automation flow: extract ClaimCenter payments via CDA every hour; identify new claimant suppliers needing Supplier Import; for new suppliers, push Supplier Import first and wait for ESS completion before pushing AP invoices; transform claim payments via crosswalk to populate AP Invoice Import FBDI; ZIP and upload; submit Load Interface File for Import via ESS; submit Payables Open Interface Import via ESS; submit Validate Payables Invoices via ESS for the loaded batch; monitor ESS job status; reconcile per claim per period. Supplier-dependency ordering is automated — no manual coordination needed.
Written-premium and paid-loss GL postings drive the largest line-item count in any P&C Fusion load. FBDI Journal Import is the template. The automation flow: extract premium transactions from PolicyCenter and paid-loss transactions from ClaimCenter via CDA; group by GL accounting period; transform via crosswalk to populate Journal Import FBDI with full segment values (legal entity, account, cost-center, intercompany, LOB, state, accident-year, Schedule P line); ZIP and upload; submit Load Interface File for Import via ESS; submit Journal Import via ESS; submit Journal Posting via ESS (for batches set to auto-post); monitor ESS job status; reconcile per GL account per period. Earning-schedule recognition runs separately via Fusion Revenue Recognition module against the loaded source transactions — written-premium is loaded directly to GL, earned-premium is recognised by Fusion against the policy-period schedule.
Oracle Fusion's Enterprise Scheduler Service (ESS) is the scheduler for every FBDI import. ESS jobs have a lifecycle (Wait → Ready → Running → Succeeded / Failed / Warning) and every load step generates an ESS request with a request ID, parent-child request hierarchy and output logs. Syntra ETL's ESS tracker captures the full lifecycle: request submitted at T+0, status polled every 30 seconds, lifecycle event logged with timestamp, output log captured on completion, failed-row diagnostics extracted from the ESS log, retry orchestrated for transient failures (database lock, supplier-master collision), permanent failures escalated to operator dashboard. The tracker provides single-pane-of-glass visibility across all in-flight ESS jobs per close cycle — operators see every batch status without logging into Fusion Scheduled Processes.
Four cadences are configurable per data domain: (1) Real-time / near-real-time — claim payments and cash receipts pushed to Fusion within 5-15 minutes of issue via REST API, supporting same-day cash position and claim-payment visibility; (2) Hourly batch — premium transactions, claim payments and cash receipts batched hourly and pushed via FBDI, supporting end-of-day reconciliation; (3) End-of-day batch — full-day's activity batched at midnight and pushed via FBDI, supporting next-morning close-readiness; (4) End-of-cycle batch — full-month's activity loaded at month-end for batch-only operations. Most P&C carriers configure differently per domain: claim payments hourly (for cash position), premium hourly (for revenue recognition), reinsurance ceded end-of-quarter (for bordereaux cycle). The cadence is per-domain configurable through the Syntra ETL admin console.
Three layers of error recovery. (1) Pre-load validation: every FBDI file validated against the current Fusion 26x release schema before submission — schema errors caught locally with row-level diagnostics, not in a 4-hour Fusion ESS job that fails on row 200,000. (2) ESS-layer recovery: ESS job failures triggered by transient issues (database lock, supplier-master collision, lookup-value mismatch) are auto-retried with exponential backoff up to 3 attempts; permanent failures escalated to operator dashboard with full ESS log. (3) Post-load reconciliation recovery: row-level reconciliation runs immediately post-load; any record that failed Fusion validation is captured in the failed-row dashboard with exact field-level reason and an action button to fix at source and replay. Replay is idempotent — replaying a successfully-loaded record has no effect.
Yes — and this is the standard pattern for large carriers still in transition to Guidewire Cloud Platform (GWCP). Multiple Guidewire source profiles are configured in parallel: GWCP source profile using CDA + Cloud API for any LOB on GWCP; legacy on-prem source profile using JDBC read-replica for any LOB still on-prem; the downstream load automation is unchanged — both source profiles feed the same crosswalk engine and produce identical Fusion FBDI output. Operators see a unified status dashboard across both source environments. This eliminates the consultant-led pattern where the GWCP-migrated LOBs and the on-prem-remaining LOBs have completely separate integration pipelines with double the operational burden.
Book a 30-minute discovery call. We will walk through your Fusion module footprint, your per-domain cadence requirements, your ESS operational SLAs and your error-recovery expectations — and have your load automation architecture sketched before the call ends.