Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for Philippines TIN #116

Open
unho opened this issue Jun 2, 2019 · 1 comment · May be fixed by #349
Open

Add support for Philippines TIN #116

unho opened this issue Jun 2, 2019 · 1 comment · May be fixed by #349

Comments

@unho
Copy link
Contributor

unho commented Jun 2, 2019

  • https://wiki.scn.sap.com/wiki/display/CRM/Philippines
  • https://help.sap.com/doc/saphelp_erp2005/6.0/ja-JP/d8/663e399265df0ee10000000a11402f/content.htm?no_cache=true

    format 999-999-999-999V for customers and vendors subject to VAT, or 999-999-999-999N for customers and vendors not subject to VAT.

  • https://www.ntrc.gov.ph/images/journal/j20141112a.pdf j20141112a.pdf (attached just in case) explains where TIN comes from, and also explains the TIN structure (originally retrieved from).

    The unique TIN consists of 9-12 digit numeric code. The first nine digits is the TIN proper and the last three digits is the branch code (in the case of business entities). The first digit thereof identifies the type of taxpayer. The digit zero ("0") signifies a corporation and digits 1 to 9 denote individual taxpayers. The succeeding 7 digits are sequential and the ninth digit is the check digit.

    In 1998, RMO 34-98 prescribed the procedures and guidelines to standardize the encoding of taxpayer's data. For individual taxpayers, TIN should be encoded in the nine-digit form of 123 - 456 - 789. If the last three characters (10th-12th digit) are not encoded, the default value should always be 000.

    In case of business entities, the TIN is usually encoded in the twelve-digit form (123-456-789-000), the last three digits of which stand for the branch code. It should be mentioned, however, that the BIR is soon to implement a thirteen-digit TIN for business entities which are operating with more than a thousand branches.

  • https://world.salestaxhandbook.com/ph-philippines

    Head office’s nine-digit TIN, plus a three-digit branch code

  • According to https://github.com/arthurdejong/python-stdnum/files/3269661/VAT_by_Countries.pdf (attached to Add support for more VAT numbers #124) it is called "Tax Identification Number" (short TIN) and it is 12 digits long (ex. xxx xxx xxx xxx).
  • https://tin-check.com/en/philippines/

    The TIN consists of 9-12 digits; the first nine digits are actual TIN, whereas the last three digits are the branch code (for corporate entities). But it is 000 for a singular citizen.

    The first nine digits or the original number of TIN identifies the citizenship category. TINs beginning with 1-9 refers to individuals. If a TIN starts with zero (0), it relates to a partnership business.

Online search:

Examples:

unho added a commit to unho/python-stdnum that referenced this issue Jan 10, 2023
@unho unho linked a pull request Jan 10, 2023 that will close this issue
@unho
Copy link
Contributor Author

unho commented Jan 10, 2023

I have been unable to find any information regarding the algorith to verify the check digit, besides that the Philippines government provides some app that allows to verify it, and there are a bunch of requests that have been denied: https://www.foi.gov.ph/requests?agency=BIR&cursor=CkYKFAoHY3JlYXRlZBIJCLWe_K7u8esCEipqCXN-ZWZvaS1waHIdCxIHQ29udGVudCIQQklSLTk1Mzk5Mjc1NzUxMAwYACAB&search=&status=

unho added a commit to unho/python-stdnum that referenced this issue Jan 10, 2023
unho added a commit to unho/python-stdnum that referenced this issue Jan 10, 2023
unho added a commit to unho/python-stdnum that referenced this issue Jan 10, 2023
unho added a commit to unho/python-stdnum that referenced this issue Jan 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants