Snapshots

Snapshots give you a defensible record of your book on any past date (back to the point in time when the snapshot production is enabled), the form regulators, auditors and finance ask for, without reprocessing a day.

The Gold data products in the Insights Data Catalog always show each record as of the last pipeline refresh. Snapshots keep a daily copy of those products as they stood at a particular moment in time, most commonly the state at the end of the banking day or when the end of day batch finished, so you can answer "what did this look like on that date" without rebuilding it from raw database transactions.

Two kinds exist: the midnight snapshot, taken at the close of the day, and the end of day snapshot, taken when Mambu's end of day processing has finished. For every intermediate state of a record, refer to Change History.

Midnight snapshot

Available on request

The midnight snapshot is an optional product. Get in touch with your Mambu Customer Success Manager to switch it on for your tenant. No change to your contract is needed.

The midnight snapshot is a daily copy of your Gold data products taken at 23:59:59 on each calendar day in your tenant's snapshot time zone. We call that moment the cut. The snapshot is taken a few minutes after local midnight, covers the day that just ended, and is stored as one new day in each product's snapshot table. Daylight saving changes are handled automatically, so the cut always falls on local midnight.

Snapshot time zone

Mambu sets the snapshot time zone for your tenant when the product is enabled. Tell your Customer Success Manager which operating time zone to use.

What a snapshot contains

Two kinds of product are snapshotted, and they are treated differently at the cut.

State products carry every record that existed at the cut, as it stood at that moment:

• Activity Log
• Branch Directory
• Client Groups
• Client Master
• Credit Arrangements
• Deposit Accounts
• Deposit Products
• General Ledger Accounts
• Loan Accounts
• Loan Products
• System Users

Transaction products carry only the rows that belong to the snapshot day, from 00:00:00 up to the cut:

• Deposit Transactions
• General Ledger Daily Summary
• General Ledger Journal Entries
• Interest Accrual Breakdown
• Loan Transactions

Snapshots cover the 16 products above. Loan Repayment Schedules and the intelligence products are not currently included.

Where the data lives and the columns added

Each product is one Delta table at midnightSnapshot/Gold/<Product> in your data lake, next to the Gold/ prefix and using the same product name, for example midnightSnapshot/Gold/LoanAccount. In Databricks the tables appear under the midnightSnapshot schema with the same names as in the gold schema.

A snapshot table has the same fields as the Gold product it copies, plus the following columns.

Column	Type	Description
snapshot_date	text, YYYY-MM-DD	The day the snapshot covers. The table is partitioned by this column.
_partition_timestamp	timestamp	When this day's snapshot was written.
_job_id	text	Identifier of the pipeline run that wrote the partition.
_build_id	text	Version of the pipeline code that wrote the partition.

Each day is one partition. If Mambu regenerates a day, for example after a data correction, the partition for that day is replaced in full, so a date never holds rows from two runs.

Querying a snapshot

Filter on snapshot_date so only the day you need is read. The example uses the Databricks schema and table names. With direct S3 access, read the Delta table at the path above instead.

SELECT encodedKey, id, accountState, balances
FROM midnightSnapshot.LoanAccount
WHERE snapshot_date = '2026-10-20';

To compare two days, read both partitions and join them on encodedKey.

SELECT a.encodedKey, a.balances AS balances_before, b.balances AS balances_after
FROM midnightSnapshot.LoanAccount a
JOIN midnightSnapshot.LoanAccount b ON a.encodedKey = b.encodedKey
WHERE a.snapshot_date = '2026-09-30' AND b.snapshot_date = '2026-10-20';

History and retention

• Snapshots begin on the day the product is enabled for your tenant. Earlier days can be generated on request, back to the date your data lake started receiving data from your Mambu core banking engine.
• Snapshot partitions are kept and are not expired automatically. They count towards your data lake storage. If you need a retention policy, discuss it with your Customer Success Manager.

Changes close to midnight

A record changed in the final second before midnight may land on either side of the cut. Where that matters, Change History carries the exact change instant.

End of day snapshot

Early access

The end of day snapshot is an early access product, available on request. Get in touch with your Mambu Customer Success Manager to discuss your requirements. Mambu enables it per tenant once the end of day completion signal from your Mambu core is connected to Mambu Insights.

Use the end of day snapshot when your reporting depends on EOD outcomes: arrears, penalties, accruals and journal summaries as Mambu's daily jobs left them.

Mambu runs end of day (EOD) processing after midnight. It updates account states, days in arrears, penalties, interest accruals and journal entry summaries for the day that just closed. The midnight snapshot is taken before that processing, so it shows the day as it was booked. The end of day snapshot is taken the moment EOD processing completes, so it shows the day as Mambu's own daily jobs left it. For more information on the processing itself, refer to End of Day Processing and Cron Jobs.

Everything else works as in the midnight snapshot: the same 16 products, the same added columns, one partition per snapshot_date, stored under eodSnapshot/Gold/<Product>. One difference applies to transaction products. Their window runs from 00:00:00 of the snapshot day until the EOD completion time, which is after that day has ended, so it can include postings made during the EOD run. Because EOD timing varies from day to day, and postings made while it runs cannot be separated from the changes EOD itself makes, treat this snapshot as the state at EOD completion rather than a strict accounting boundary.

Enabling snapshots

• Both snapshot kinds are enabled per tenant on request through your Mambu Customer Success Manager or request it through the Insights UI.
• They consume Mambu Insights Credits like any other data product: compute for each run and storage for the partitions they keep. For more information, refer to Pricing and Consumption.
• Once enabled, snapshot tables appear on the Data Products Dashboard with their kind, next to the Gold products. For more information, refer to Operations and Monitoring.
• Their catalog entries are listed under Snapshots. For every intermediate state of a record, rather than one state per day, refer to Change History.