Baton Rouge & East Baton Rouge Parish Spending - Every Payment
Pricing
from $0.03 / 1,000 baton rouge payment records
Baton Rouge & East Baton Rouge Parish Spending - Every Payment
Every payment line the City-Parish of Baton Rouge has issued (public open data, 1.26M lines, FY2018-today): vendor and its diversity classification, department, fund, program, expense category and commodity, plus the invoice and check behind it. Filter by vendor, department, amount or date.
Pricing
from $0.03 / 1,000 baton rouge payment records
Rating
0.0
(0)
Developer
Wenhao Yang
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Share
Every payment line the City of Baton Rouge / East Baton Rouge Parish has cut, straight from the City-Parish's own accounting system. 1.26 million payment lines, from fiscal 2018 through today.
Low cost
From $0.00005 per record, down to $0.00003 at Gold. Pay only for the records you actually receive - the whole register stays queryable, you are never billed for the scan behind it.
What you get
One row per invoice line the Parish paid, with the money and the supplier's profile attached to it:
- Who was paid - vendor name, city, state and ZIP, plus the vendor's diversity classification
- Who spent - the department, division, purchasing department, program, subprogram and government function
- Out of what - the fund
- On what - the expense category and the commodity code and description
- How much - the line amount, the check number and date, the invoice number and date, and the purchase order / contract the line draws against
Supplier diversity is the deep part
Each line carries the Parish's own classification of the vendor as a set of clean Y/N flags you can filter on directly:
minorityOwned,disadvantagedOwned,disabledVeteranOwnedsmallMinorityOwned,smallWomanOwned,smallVeteranOwned,smallMinorityWomanOwned,smallDisabledVeteran,smallDisadvantagedOwned,smallNonMinorityOwnedindependentContractor
Slice a department's spend by the kinds of suppliers it actually reaches.
Filter it
- Vendor -
vendorName="FIRE"finds every payment to that supplier. - Department / division / program -
department="LIBRARY",division="FIRE PROTECT",program="PUBLIC SAFETY". - Where the money came from -
fund="GENERAL". - Amount -
minAmount=10000for five-figure lines (and up). - Date -
checkFrom="2026-01-01"for this year's checks. - Diversity -
minorityOwned="Y"for minority-owned suppliers only.
Example inputs
Payments to one supplier - vendorName is a substring match.
{ "vendorName": "FIRE", "maxResults": 25 }
A department's year - combine department and date.
{ "department": "LIBRARY", "checkFrom": "2026-01-01", "maxResults": 50 }
Minority-owned spend - one flag.
{ "minorityOwned": "Y", "maxResults": 50 }
Where the money goes - mode=aggregate returns one count row per department;
every group comes back.
{ "mode": "aggregate", "groupBy": "department" }
Or roll it up
Set mode=aggregate and get a rolled-up count by fiscal year,
department, division, program, function, expense category,
payment type, payment status, vendor state, vendor type or
fund. Every group comes back - this mode is not cut off by maxResults.
Then follow the money
- Every line a supplier has been paid from the Parish, and for what.
- A department's spend by fund, by program, by expense category (aggregate mode counts the lines in each - one dimension per run).
- Diversity spend: filter to minority-, woman-, veteran-owned or small-business lines and compare the counts across runs.
- Recent checks first - the newest check date leads; use
minAmountto zero in on larger payments.
Example output
One payment line - vendorName=FIRE:
{"platform": "ebr-spending","source": "east-baton-rouge-parish-spending","mode": "rows","fiscalYear": "2026","department": "FIRE PROTECTION DISTRICTS","vendorName": "BROWNSFIELD FIRE DEPARTMENT","checkNumber": "8055","checkDate": "2026-10-02","amount": "76.48","expenseCategory": "EDUCATIONAL ALLOWANCES","paymentStatus": "Cleared","minorityOwned": "N","vendorCity": "BATON ROUGE","vendorState": "LA"}
mode=aggregate, groupBy=department - one count row per department:
OTHER 457,509ENVIRONMENTAL SERVICES 96,097FLEET MANAGEMENT 78,569CLERK OF COURT 71,032LIBRARY BOARD OF CONTROL 63,468HUMAN DEVELOPMENT AND SERVICES 39,511
Notes on the data, from the source
- A row is an invoice line, not a payment. One check pays many invoices and
an invoice can carry many lines.
checkNumberis the payment; the amount is the line. - Reversals are in here. 10,656 rows are negative - real accounting
entries, returned as they stand. Set
minAmount=0.01for spending only. - The diversity flags follow the vendor, so they are present on the ~86% of
lines that carry a vendor name - the same coverage as
vendorName. Where the Parish holds a fuller profile,vendorGender,vendorEthnicityandvendorClassare added, and read as sentinel text ("NOT PROVIDED") rather than blank. - Not every line has a vendor. ~86% carry a
vendorName; the rest are internal transfers with no supplier. sourceUpdatedAtcarries the newest check date, the freshness signal an agent can read without running the actor.
