Commit Graph

6 Commits (d67635d3386caceffbaea1c79c73e2787524aeed)

Author SHA1 Message Date
q3k 220c5d24a3 invoice: move validation to separate layer, validate GTU/SP codes
Change-Id: I0af85b054356eaae81b528e5e64bf74c10bd3ae4
2020-11-16 22:04:23 +01:00
q3k d9f912378d invoice: add GTU and SP codes
These are codes defined in JPK_V7, ie. the control file submitted to
Polish tax authorities for all invoices created in a given month. We
need to now tag our invoices with the appropriate codes when submitting
them to our accountants, which will pass them on over to the tax
authoritiex in a JPK_V7M file.

This only adds the relevant enums and adds them to proto messages, but
does not actually implement any control/model logic.

Change-Id: I695d05b55143a248dab9346151da3c572c7665d4
2020-11-16 20:38:08 +00:00
q3k de3d3fa641 bgpwtf/invoice: hide invoicee VAT number when not given
Also re-add go-bindata to WORKSPACE, something nuked it.

Change-Id: I723ebee7f843d0135a3e1121e2e93ae5fe56bc4b
2020-05-31 00:12:11 +02:00
q3k 572d766096 bgpwtf/invoice: bump for 2020
This doesn't automatically bump generated numbers - however, new users
will at least have sensible IDs now :).

To bump an existing deployment, you will have to do some mild surgery:

 - edit the touched query to once generate a new, appropriate serial
   (eg. 20001)
 - run and seal one invoice
 - restore original code (now with the new 20000 default)

In the future we should have an RPC override for the new sealed final
UID with some basic sanity checks.

Change-Id: Idd8187618869f6ea76f1b187acfbdd2f1c94005b
2020-01-14 14:03:38 +01:00
q3k 1446e98beb proto/invoice -> bgpwtf/invoice/proto
Change-Id: I5d25864046665e4b0e57ec62a29797fbce6ed3cb
2019-07-21 16:04:23 +02:00
q3k cea71e3be8 go/svc/{invoice,speedtest} -> bgpwtf/
Continued from https://gerrit.hackerspace.pl/c/hscloud/+/71 .

Change-Id: I5aef587c7e9a4cec301e3c95530c33914851ad44
2019-07-21 15:30:08 +02:00