Skip to content

How to

Next month's statement, zero rework

If you pull the same table out of a PDF every month, set it up once. The way Mammoth read the first statement is saved with the dataset, so next month's comes out in the same columns.

58 seconds, real app, made-up bank statements. Follow along with the same two: October statement (PDF) and November statement (PDF). Download the video (MP4)

The steps

  1. 1

    Upload the first statement

    In Data, choose New dataset and upload the PDF. Here, a two-page business account statement for October.

  2. 2

    Choose what to import

    Mammoth shows the PDF next to the choices. For a statement, choose Only tables, then Extract.

    The Review data import window: the October statement on the left, and What to import on the right with Only tables selected
  3. 3

    Check the table

    The table runs across both pages, and Mammoth reads it as one: 30 rows with Date, Description, Debit, Credit and Balance. If it looks right, choose Looks right, then Make a new dataset and Create dataset.

    Table 1, pages 1 to 2, 5 columns and 30 rows, starting with 01 Oct 2026 Client payment rows
  4. 4

    The recipe is saved

    The dataset keeps how the PDF was read. Settings & history lists it as the Recipe. Rename the dataset if you like; here it's Bank statements.

    The Bank statements dataset: 30 rows, 5 columns, and Settings & history showing 1 batch, Add to existing data, Recipe
  5. 5

    Add next month's statement

    When November's statement arrives, select the dataset, choose Add data, upload the PDF and choose Submit. The recipe reads it with no review step, and its rows go in after October's: 60 in all.

    The table in Explore where October ends at row 30 and November starts at row 31, in the same five columns

Good PDFs for a recipe

A recipe suits a PDF that arrives in the same layout every month.

  • Bank and card statements
  • Supplier statements and remittance advice
  • Monthly reports exported from another system

Start from a normal month. A statement with an unusual extra page or table makes a less reliable recipe.

If it doesn’t look right

Check each month's row count
Open Settings & history and expand Batches. Each statement is listed as a batch with its row count. Compare it with the number of lines on the PDF, especially when the statement looks different from last month's.
The same payee shows up twice
PDFs aren't always consistent. One month can write “Client payment - Oakline” and the next “Client payment – Oakline”. Add a Find & Replace step in Explore to make them match; it runs on every month.
You want different columns
Read the first statement again with Custom and describe the fields you want. That becomes the recipe for the months after.

Every month after

Each statement you add with Add data goes through the same recipe, and any steps you add in Explore run on its rows too.
Add or replace data in the docs

Try it with two months of your own statements.

Read the first once, add the second with Add data, and check the row count.

  • ✓ 14-day Pro trial
  • ✓ No credit card
  • ✓ Viewers always free