afip 0.0.1

Python package to interact with some of Argentina's AFIP Web services.

python-afip

Python package to interact with some of Argentina's AFIP Web services.

NOTE: UNDER DEVELOPMENT. MUCH OF THIS IS NOT IMPLEMENTED YET

It implements programmatic interfaces for the following services:

• WSAA: the token-granting service.
• WSFE: the invoicing ("factura") service for the local market (type "C" invoices).
• WSFEX: the invoice service for export operations (type "E" invoices).

It's designed to contain anything a monotributista freelancer reasonably needs to issue and manipulate invoices, presumably to send something that doesn't look completely horrendous and unprofessional to clients (I'm looking at you, RECE et al.)

This is a Python 3 ONLY library, seeing as Python 2.7 will reach end of life in short order.

This package only contains the base interfaces to interact with AFIP's Web services. It doesn't implement a DB backend to store things on, an administrative interface of any kind, or an invoice/receipt template-to-PDF generator. It does, however, include a CLI utility to test things out.

Tested only on Linux as that's what I use, but there is nothing platform-specific about it. If you use it on Mac/Windows/whatever and it something doesn't work, kindly submit a pull request or at least file a bug.

Contribution in the form of bug fixes, documentation, code improvements, tests, support for additional services.

You might notice there is another package available for Python to interact with AFIP's services called pyafipws and you might be wondering why use this one instead. To that, I can tell you why I'm writing it:

• This is a simpler, one-function-one-package sort of deal. Use it to build something else.
• It runs on Python 3 out of the box.
• The code is simpler/cleaner to understand.
• This package tries to abstract away (i.e. hide) some of the inherent ugliness in the native interfaces to the extent that's possible.

And just to be fair, a few reasons not to use it:

• You want something established and better tested.
• You need services not currently supported.
• You don't care about Python 3 (though you should, it's nicer).
• You aren't looking to integrate this into something else. You want a fully built out solution.

TODO

• Document how to get valid certificates.
• Document basic usage.
• Document API in code for API reference doc gen.
• Write CLI tool.
• Implement WSFE.
• Implement WSFEX.
• Look into other WS I might need, and implement those.
• Implement output of invoices into whatever storage format AFIP requires as well as something nicer to deal with.

Logging

In the event anything goes wrong either in this package or in your own application code, and given the irrevocable nature of issuing an invoice through AFIP (why?!), good logging is essential. So, all interfaces run a logging plugin on the underlying SOAP client.

All you need to do is pass the log_dir argument to the constructor of any WS interface. You'll get jsonlines-formatted files with every request and response sent/received along with the raw XML and timestamps for whatever service you called.

I strongly encourage you to use this. Worst-case scenario, you'll have a small log directory to clean up every now and then.