Carrier SFTP

Carrier SFTP integration that pulls your book on autopilot

Enter each carrier’s SFTP credentials once. AgencyGrid detects new file drops, handles whatever encoding and delimiter the carrier used, maps the columns, dedupes the rows, and quarantines anything it cannot trust, so book and commission files load without anyone logging into a portal.

Start free trial Explore the platform

Carriers do not offer clean APIs. What they offer is a folder on an SFTP server where book-of-business and commission files land on their own schedule, in their own format, named however that carrier happens to name things. Agencies deal with this by having someone log in, download files, and paste them into spreadsheets. Every carrier, every cycle.

AgencyGrid turns that folder into a managed pipeline that feeds your book of business reporting. You store the credentials once, encrypted, and a scheduled worker watches the folder, picks up new files as they appear, and runs each one through detection, mapping, and dedupe before it ever reaches your book. The portal logins stop.

Set up a carrier once, then forget it

Onboarding a carrier is a one-time step: provide the host, the credentials, and the folder path. AgencyGrid encrypts those credentials with AES-256 envelope encryption and stores them as tenant data. The connection is yours alone, isolated from every other agency on the platform.

From then on the worker connects on a schedule, lists the folder, and identifies which files are new since the last run. Nothing is downloaded twice, and no human has to remember to check.

✓ Credentials encrypted at rest, scoped to your org
✓ Scheduled polling: new files picked up automatically
✓ Book and commission files handled on the same connection

Detection, encoding, and column mapping

Carrier files are inconsistent in every way that matters. One drops a UTF-8 CSV, the next a Latin-1 file with a pipe delimiter, a third an Excel export with a header row three lines down. AgencyGrid detects the file type, resolves the encoding and delimiter, and finds the real header before it tries to read a single row.

Then it maps the carrier’s columns to your normalized schema. Familiar layouts map on sight; new or changed ones get AI-assisted suggestions that you confirm once, after which that carrier’s mapping is remembered for every future drop.

Dedupe and quarantine keep the book clean

Carriers re-send files, overlap date ranges, and occasionally deliver something malformed. Loading that blindly double-counts premium and corrupts the book. AgencyGrid dedupes each load against what it has already ingested, so a re-sent file changes nothing, and quarantines any file or row it cannot parse or trust instead of letting it through, protecting downstream numbers like policy persistency reporting that depend on clean status data.

Quarantined items are held for review with the reason attached, so a broken feed is visible and fixable, never a silent gap in your numbers.

✓ Re-sent and overlapping files deduped on load
✓ Malformed files quarantined, not silently dropped
✓ Every raw file retained in encrypted storage

What the pipeline handles

From carrier folder to clean book

Scheduled auto-pull

New file drops detected and downloaded on schedule. No manual portal runs.

Encoding and layout aware

Delimiter, encoding, and header row resolved before any row is read.

✓ AI-assisted column mapping
✓ Mappings remembered per carrier

Dedupe and quarantine

Re-sends never double-count; unparseable files are held for review.

Credentials encrypted

SFTP logins stored with AES-256 envelope encryption, isolated per tenant.

FAQ

Common questions

How does carrier SFTP integration work?

You provide each carrier’s SFTP host, credentials, and folder path once. AgencyGrid encrypts them, then a scheduled worker polls the folder, downloads new book and commission files, and runs each through detection, mapping, dedupe, and quarantine before loading it into your book.

Do I have to map columns for every carrier?

Only the first time. AgencyGrid recognizes familiar layouts automatically and offers AI-assisted mapping suggestions for new ones. Once you confirm a carrier’s mapping, it is remembered and reused for every future file from that carrier.

What happens when a carrier re-sends a file?

Nothing bad. Every load is deduped against what has already been ingested, so a re-sent or overlapping file does not double-count premium or commission. Only genuinely new records change the book.

Are the SFTP credentials secure?

Yes. Carrier credentials are tenant data, encrypted at rest with AES-256-GCM envelope encryption, with the master key held only in deployment environment variables. Each agency’s connection is isolated from every other tenant.

Keep exploring

Related guides

Part of Book of Business Reporting

Book of Business ReportingConsolidate every in-force policy into one live, hierarchy-aware view.

Policy Persistency ReportingTrack retention, lapse, and persistency across your whole book.Medicare AEP & OEP ReportingSeason-ready production and enrollment reporting for Medicare shops.Book of Business ValuationUnderstand what an agency book is worth before you buy, sell, or borrow.Agency Reporting SoftwareBuild and schedule production, book, and commission reports for every level of the downline.

From the blog

Connecting Carrier SFTP Feeds: What Agencies Get WrongA carrier SFTP feed is the difference between a book of business that updates itself and one you rebuild in a spreadsheet every month. Most agencies stumble on the same handful of details.

Connect your first carrier feed

Store the credentials once and let book and commission files pull, map, and load themselves.

Start your 14-day free trial View pricing