Might be worth looking when working with this issue, #640

Based on Slack discussion, the team agrees that this is something to go ahead with. After the changes have been merged, announce it on Community Team P2.

Few questions for @harmonyromo and @ciudadanoB:

When WordCamp is not using WPCS accounts for Camptix payment processing, should the invoice have something else than WPCS as a sender? Or should we use the WordCamp tracker's "Running money through WPCS" field to determine this? Or can the sender be always WPCS?

Do you see any reasons why the VAT field should not be automatically enabled for all invoice requests?

Currently, the invoice number format is {site-id}-{invoice-id}, where the invoice-id is a running number on a single WordCamp, not across all WordCamps. Is this format ok or would you like to change it?

Are there any reasons why the invoice-number should reset when the year changes? In case it resets, the invoice number format is {site-id}-{invoice-id}-{year}. To me year in invoice number and resetting the ID every year sounds like it can cause some troubles.

Should we use the WordCamp tracker's "Running money through WPCS" field to determine this?

Hmm… I don't know how this works. If a WC is not running money through WPCS, can they still use Camptix with a local payment processor plugin associated to their own account? Or all the payment plugins installed are tied to WPCS? Because that changes things.

I mentored a WordCamp that used a third-party external vendor for ticketing, so in that case we can't issue invoices (it should be the platform the one to handle that) so it would be important to check if they're not running money through WPCS. But not sure about all the cases with processors. Probably @harmonyromo has more info about this!

Do you see any reasons why the VAT field should not be automatically enabled for all invoice requests?

No… I mean, if you're asking for an invoice you will for sure add your VAT number so you can use it for your financial papers, right?

Are there any reasons why the invoice-number should reset when the year changes? In case it resets, the invoice number format is {site-id}-{invoice-id}-{year}. To me year in invoice number and resetting the ID every year sounds like it can cause some troubles.

In Spain is typical to reset the number every year, so each year is like its own series (2023/001, 2023/002… or 001/2023, 002/2023). As far as we have different numbers generated for each invoice, I don't see it like a problem. I know in the US they don't care as much as we do with invoice numbers, right? (I mean, here you must have all the invoices with consecutive numbers or you're in trouble). But {site-id}-{invoice-id}-{year} looks ok to me.

If a WC is not running money through WPCS, can they still use Camptix with a local payment processor plugin associated to their own account? Or all the payment plugins installed are tied to WPCS?
If a WC is not running funds through WPCS, the team can still use Camptix with a local payment processor plugin. I these cases, the funds will go directly to the organizing team. I know often, in these cases, there will be an organizer who uses their business account to handle all fund receipts and payments, so having WPCS listed may not work.

Do you see any reasons why the VAT field should not be automatically enabled for all invoice requests?
I think as long as this isn't a required field it will be fine. In the US, our rules are much different, so that is a number US residents would not have.

Are there any reasons why the invoice-number should reset when the year changes? In case it resets, the invoice number format is {site-id}-{invoice-id}-{year}. To me year in invoice number and resetting the ID every year sounds like it can cause some troubles.
This is not something I have a preference on either. Whatever is easiest works for me.

Thank you, Juan and Harmony!