Invoice Ninja node - Expense date does not work

Wade0 · January 7, 2026, 4:46am

Describe the problem/error/question

The Invoice Ninja create an expense node does not send Expense date

What is the error message (if any)?

The field is expenseDate when it should just be date

Information on your n8n setup

n8n version: 2.2.4
Database (default: SQLite): SQLite
n8n EXECUTIONS_PROCESS setting (default: own, main): Own
Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
Operating system: Ubuntu 24.04

Wouter_Nigrini · January 7, 2026, 8:14am

Hi @Wade0,

please can you share your workflow in a code block so we can better understand what is going on in your workflow

Wade0 · January 7, 2026, 9:04am

As per screenshot the Expense date in the nodes backend is not sending to date as it is set to expenseDate and not date.

Nayan_Thakor · January 7, 2026, 9:18am

Hi @Wade0,
It seems to be an issue with the Data Type mismatch.
Try using {{ $luxon.DateTime.fromISO($json.date).toFormat(‘yyyy-MM-dd HH:mm:ss’) }}.
Adjust the format according to the expected format.

Wade0 · January 7, 2026, 9:34am

It’s not writing anything to date that’s why its filling in Todays date due to a field-name mismatch between:

what Invoice Ninja’s API expects (date, payment_date in Y-m-d), and
what the n8n Invoice Ninja node is actually sending (it looks like it’s using expenseDate internally).

Wade0 · January 7, 2026, 10:24am

Here is the problem should be body.date

Wouter_Nigrini · January 7, 2026, 11:54am

Hi @Wade0 ,

According to the invoice ninja api code for the expense model, it is definitely expecting “exepense_date”

github.com/invoiceninja/invoiceninja

app/Models/Expense.php

master


      
           */
          protected $presenter = 'App\Ninja\Presenters\ExpensePresenter';
          
          /**
           * @var array
           */
          protected $fillable = [
              'client_id',
              'vendor_id',
              'expense_currency_id',
              'expense_date',
              'invoice_currency_id',
              'amount',
              'foreign_amount',
              'exchange_rate',
              'private_notes',
              'public_notes',
              'bank_id',
              'transaction_id',
              'expense_category_id',
              'tax_rate1',

Wouter_Nigrini · January 7, 2026, 1:22pm

Hi @Wade0,

Ok so I installed invoice ninja locally and tested your claims. While expense_date is the valid and correct field for the expense request, it seems like this is a problem in invoice ninja itself ignoring the expense_date field. You seem to be correct that ‘date’ will set the actual date. I tested this both with the ninja node as well as making a direct http rest call to their API. Same results.

However, when using the http node and setting ‘date’, it seems like invoice ninja does use this as the date.

Thus, I wouldnt call this a bug in n8n’s invoice ninja node, however maybe a suggested enhancement to add the “Date” field as a possible input.

Having all that said, maybe for now, just use the http rest call direct when dealing with Expense creation if you want to set the date. See below example:

And when using the date in the rest http node, it does work:

Wade0 · January 7, 2026, 3:17pm

@Wouter_Nigrini Thanks for the extra insight. I am using the Http node for now.

Wade0 · January 7, 2026, 7:58pm

Ok I see now I am using v5-Stable and expense_date is used in the Master branch.

Guess I’m going to have to wait for that to be pushed to Stable

Thanks all for the help.

system · January 14, 2026, 7:59pm

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.