Files

1095 lines
61 KiB
XML

<?xml version="1.0" encoding="utf-8"?>
<root>
<!--
Microsoft ResX Schema
Version 2.0
The primary goals of this format is to allow a simple XML format
that is mostly human readable. The generation and parsing of the
various data types are done through the TypeConverter classes
associated with the data types.
Example:
... ado.net/XML headers & schema ...
<resheader name="resmimetype">text/microsoft-resx</resheader>
<resheader name="version">2.0</resheader>
<resheader name="reader">System.Resources.ResXResourceReader, System.Windows.Forms, ...</resheader>
<resheader name="writer">System.Resources.ResXResourceWriter, System.Windows.Forms, ...</resheader>
<data name="Name1"><value>this is my long string</value><comment>this is a comment</comment></data>
<data name="Color1" type="System.Drawing.Color, System.Drawing">Blue</data>
<data name="Bitmap1" mimetype="application/x-microsoft.net.object.binary.base64">
<value>[base64 mime encoded serialized .NET Framework object]</value>
</data>
<data name="Icon1" type="System.Drawing.Icon, System.Drawing" mimetype="application/x-microsoft.net.object.bytearray.base64">
<value>[base64 mime encoded string representing a byte array form of the .NET Framework object]</value>
<comment>This is a comment</comment>
</data>
There are any number of "resheader" rows that contain simple
name/value pairs.
Each data row contains a name, and value. The row also contains a
type or mimetype. Type corresponds to a .NET class that support
text/value conversion through the TypeConverter architecture.
Classes that don't support this are serialized and stored with the
mimetype set.
The mimetype is used for serialized objects, and tells the
ResXResourceReader how to depersist the object. This is currently not
extensible. For a given mimetype the value must be set accordingly:
Note - application/x-microsoft.net.object.binary.base64 is the format
that the ResXResourceWriter will generate, however the reader can
read any of the formats listed below.
mimetype: application/x-microsoft.net.object.binary.base64
value : The object must be serialized with
: System.Runtime.Serialization.Formatters.Binary.BinaryFormatter
: and then encoded with base64 encoding.
mimetype: application/x-microsoft.net.object.soap.base64
value : The object must be serialized with
: System.Runtime.Serialization.Formatters.Soap.SoapFormatter
: and then encoded with base64 encoding.
mimetype: application/x-microsoft.net.object.bytearray.base64
value : The object must be serialized into a byte array
: using a System.ComponentModel.TypeConverter
: and then encoded with base64 encoding.
-->
<xsd:schema id="root" xmlns="" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
<xsd:import namespace="http://www.w3.org/XML/1998/namespace" />
<xsd:element name="root" msdata:IsDataSet="true">
<xsd:complexType>
<xsd:choice maxOccurs="unbounded">
<xsd:element name="metadata">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="value" type="xsd:string" minOccurs="0" />
</xsd:sequence>
<xsd:attribute name="name" use="required" type="xsd:string" />
<xsd:attribute name="type" type="xsd:string" />
<xsd:attribute name="mimetype" type="xsd:string" />
<xsd:attribute ref="xml:space" />
</xsd:complexType>
</xsd:element>
<xsd:element name="assembly">
<xsd:complexType>
<xsd:attribute name="alias" type="xsd:string" />
<xsd:attribute name="name" type="xsd:string" />
</xsd:complexType>
</xsd:element>
<xsd:element name="data">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
<xsd:element name="comment" type="xsd:string" minOccurs="0" msdata:Ordinal="2" />
</xsd:sequence>
<xsd:attribute name="name" type="xsd:string" use="required" msdata:Ordinal="1" />
<xsd:attribute name="type" type="xsd:string" msdata:Ordinal="3" />
<xsd:attribute name="mimetype" type="xsd:string" msdata:Ordinal="4" />
<xsd:attribute ref="xml:space" />
</xsd:complexType>
</xsd:element>
<xsd:element name="resheader">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
</xsd:sequence>
<xsd:attribute name="name" type="xsd:string" use="required" />
</xsd:complexType>
</xsd:element>
</xsd:choice>
</xsd:complexType>
</xsd:element>
</xsd:schema>
<resheader name="resmimetype">
<value>text/microsoft-resx</value>
</resheader>
<resheader name="version">
<value>2.0</value>
</resheader>
<resheader name="reader">
<value>System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
</resheader>
<resheader name="writer">
<value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
</resheader>
<data name="AccountPlan_AddAccount" xml:space="preserve">
<value>add account</value>
<comment>Displayed as link in parens after account group name</comment>
</data>
<data name="AccountPlan_CreateRootAccount" xml:space="preserve">
<value>Create new root account</value>
</data>
<data name="AccountPlan_DebtBalancesAreNegative" xml:space="preserve">
<value>This is a Liabilities account. Such accounts normally have a balance in the negative, since they represent negative assets in the organization. Your entered initial balance was changed to negative.</value>
</data>
<data name="AccountPlan_Edit_AccountName" xml:space="preserve">
<value>Account name</value>
</data>
<data name="AccountPlan_Edit_ActiveLong" xml:space="preserve">
<value>Is this account open for transactions?</value>
</data>
<data name="AccountPlan_Edit_ActiveShort" xml:space="preserve">
<value>Active</value>
</data>
<data name="AccountPlan_Edit_AdministrativeLong" xml:space="preserve">
<value>Is this an account after the EBITDA line?</value>
<comment>Earnings before interest, tax, depreciation and amortization (EBITDA) is a measure of a company's operating performance.</comment>
</data>
<data name="AccountPlan_Edit_AdministrativeShort" xml:space="preserve">
<value>Admin</value>
</data>
<data name="AccountPlan_Edit_BudgetBalance" xml:space="preserve">
<value>Budget (balance is &lt;span id="SpanTextCurrency"&gt;foo&lt;/span&gt; &lt;span id="SpanEditBalance"&gt;bar&lt;/span&gt;)</value>
<comment>foo, bar replaced on load with actual values</comment>
</data>
<data name="AccountPlan_Edit_ExpensableLong" xml:space="preserve">
<value>Can people use this account for expense reports?</value>
</data>
<data name="AccountPlan_Edit_ExpensableShort" xml:space="preserve">
<value>Expensable</value>
</data>
<data name="AccountPlan_Edit_FileUploadProfile" xml:space="preserve">
<value>Automation Profile</value>
</data>
<data name="AccountPlan_Edit_Header" xml:space="preserve">
<value>Editing Account</value>
</data>
<data name="AccountPlan_Edit_HeaderAutomation" xml:space="preserve">
<value>Automation</value>
<comment>Automatic connections to bank, blockchain etc.</comment>
</data>
<data name="AccountPlan_Edit_HeaderConfiguration" xml:space="preserve">
<value>Configuration</value>
</data>
<data name="AccountPlan_Edit_HeaderDailyOperations" xml:space="preserve">
<value>Daily Operations</value>
</data>
<data name="AccountPlan_Edit_InitialBalance" xml:space="preserve">
<value>Initial Balance (inbound into {0}), {1}</value>
<comment>{0} is the first ledger year in Swarmops. {1} is the currency code.</comment>
</data>
<data name="AccountPlan_Edit_Parent" xml:space="preserve">
<value>Parent account or group</value>
</data>
<data name="AccountPlan_ExpensesBudgetsAreNegative" xml:space="preserve">
<value>This is an Expenses account. Such accounts normally have a budget in the negative, since they drain assets from the organization. Your proposed budget was changed to negative.</value>
<comment>Displayed as a message box</comment>
</data>
<data name="AccountPlan_Header_AccountName" xml:space="preserve">
<value>Account</value>
</data>
<data name="AccountPlan_Header_Balance" xml:space="preserve">
<value>Balance</value>
</data>
<data name="AccountPlan_Header_Budget" xml:space="preserve">
<value>Budget</value>
</data>
<data name="AccountPlan_Header_Edit" xml:space="preserve">
<value>Edit</value>
</data>
<data name="AccountPlan_Header_Flags" xml:space="preserve">
<value>Flags</value>
</data>
<data name="AccountPlan_Info" xml:space="preserve">
<value>This is the overview of the financial accounts in your bookkeeping ledger. You can do some maintenance from here, even if most of the daily operations should be delegated to the budget owners.</value>
</data>
<data name="AccountPlan_NewAccount" xml:space="preserve">
<value>New Account</value>
<comment>the name of newly-created accounts, before rename</comment>
</data>
<data name="AccountPlan_Options_ShowInactive" xml:space="preserve">
<value>Show Inactive Accounts (&lt;span id="SpanInactiveCount"&gt;{0:N0}&lt;/span&gt;)</value>
<comment>The {0} is the number of inactive accounts.</comment>
</data>
<data name="AccountPlan_PageTitle" xml:space="preserve">
<value>Chart of Accounts</value>
</data>
<data name="AccountPlan_ProjectedLoss" xml:space="preserve">
<value>Projected Loss {0}</value>
<comment>"Projected" as in "Budgeted". {0} is year.</comment>
</data>
<data name="AccountPlan_ProjectedProfit" xml:space="preserve">
<value>Projected Profit {0}</value>
<comment>"Projected" as in "Budgeted". {0} is year.</comment>
</data>
<data name="BalanceSheet_AccountName" xml:space="preserve">
<value>Account</value>
</data>
<data name="BalanceSheet_Assets" xml:space="preserve">
<value>Assets XXXX</value>
<comment>For the simplified view - XXXX is replaced with year</comment>
</data>
<data name="BalanceSheet_AssetsDelta" xml:space="preserve">
<value>(change)</value>
<comment>Change from previous year's close, which is same as from start of this year</comment>
</data>
<data name="BalanceSheet_ContentHeader" xml:space="preserve">
<value>Balance Sheet for {0},</value>
<comment>{0} is the organization name. The year follows immediately, so keep ending comma.</comment>
</data>
<data name="BalanceSheet_Current" xml:space="preserve">
<value>Current</value>
</data>
<data name="BalanceSheet_DownloadFileName" xml:space="preserve">
<value>BalanceSheet</value>
<comment>Must ONLY contain A-Z, a-z characters - nothing accented!</comment>
</data>
<data name="BalanceSheet_EndYear" xml:space="preserve">
<value>End-XXXX</value>
<comment>The XXXX is replaced with year number.</comment>
</data>
<data name="BalanceSheet_Info" xml:space="preserve">
<value>The Balance Sheet is an overview of assets and debts at a snapshot in time, and is used to see how results affect the overall financial health of the organization. You may also want to look at the &lt;a href="ProfitLossStatement"&gt;profit-and-loss statement&lt;/a&gt; which is the overview of income and expenditure.</value>
</data>
<data name="BalanceSheet_Info_Simplified" xml:space="preserve">
<value>The Balance Sheet is an overview of assets and debts at a snapshot in time, and is used to see how results affect the overall financial health of the organization. You may also want to look at the &lt;a href="BalanceSheet"&gt;advanced balance sheet&lt;/a&gt; for more detail, or the &lt;a href="ProfitLossStatement"&gt;profit-and-loss statement&lt;/a&gt; which is the overview of income and expenditure.</value>
</data>
<data name="BalanceSheet_Liabilities" xml:space="preserve">
<value>Liabilities XXXX</value>
<comment>For the simplified view - XXXX is replaced with year</comment>
</data>
<data name="BalanceSheet_LiabilitiesDelta" xml:space="preserve">
<value>(change)</value>
<comment>Change from previous year's close, which is same as from start of this year</comment>
</data>
<data name="BalanceSheet_LossToDate" xml:space="preserve">
<value>Loss to date ({0})</value>
<comment>The {0} is the year of the report</comment>
</data>
<data name="BalanceSheet_PageTitle" xml:space="preserve">
<value>Balance Sheet</value>
</data>
<data name="BalanceSheet_ProfitToDate" xml:space="preserve">
<value>Profit to date ({0})</value>
<comment>The {0} is the year of the report</comment>
</data>
<data name="BalanceSheet_Q1" xml:space="preserve">
<value>Change Q1</value>
</data>
<data name="BalanceSheet_Q2" xml:space="preserve">
<value>Change Q2</value>
</data>
<data name="BalanceSheet_Q3" xml:space="preserve">
<value>Change Q3</value>
</data>
<data name="BalanceSheet_Q4" xml:space="preserve">
<value>Change Q4</value>
</data>
<data name="BalanceSheet_StartYear" xml:space="preserve">
<value>Start-XXXX</value>
<comment>The XXXX is replaced with year number.</comment>
</data>
<data name="BalanceTransactions_Error_NeedDescription" xml:space="preserve">
<value>The transaction description cannot be empty.</value>
</data>
<data name="BalanceTransactions_Error_NeedDocumentation" xml:space="preserve">
<value>The transaction needs a proof of purchase.</value>
</data>
<data name="BalanceTransactions_Error_VatAmountParseError" xml:space="preserve">
<value>The VAT amount doesn't seem to be correctly entered.</value>
</data>
<data name="BalanceTransactions_ExactMatches" xml:space="preserve">
<value>Exact Matches For This Amount</value>
<comment>Header in selection list. Capitalize as customary for culture.</comment>
</data>
<data name="BalanceTransactions_ExactMatchesFarAway" xml:space="preserve">
<value>Matching Amount But On Unexpected Date/Time</value>
<comment>Header in selection list. Capitalize as customary for culture.</comment>
</data>
<data name="BalanceTransactions_FivePercentMatches" xml:space="preserve">
<value>Amount Within 5% Tolerance</value>
<comment>Header in selection list. Capitalize as customary for culture.</comment>
</data>
<data name="BalanceTransactions_GridHeader_AccountName" xml:space="preserve">
<value>Account</value>
<comment>Usually the account name. Can also be "several".</comment>
</data>
<data name="BalanceTransactions_GridHeader_Amount" xml:space="preserve">
<value>Amount</value>
</data>
<data name="BalanceTransactions_GridHeader_Description" xml:space="preserve">
<value>Description</value>
</data>
<data name="BalanceTransactions_GridHeader_TransactionId" xml:space="preserve">
<value>Tx#</value>
<comment>Keep VERY short.</comment>
</data>
<data name="BalanceTransactions_HeaderUnbalancedTransactions" xml:space="preserve">
<value>Dangling Payments (Must Balance, Match, or Fix)</value>
<comment>A "dangling payment" is a transaction that's not yet completed to have equal parts debit and credit. Typically, it's a payment that hasn't been identified.</comment>
</data>
<data name="BalanceTransactions_Info" xml:space="preserve">
<value>Some auto-imported financial transactions can't be automatically matched to the ongoing accounting. This is where you manually match such transactions to "balance" them (if a transaction only has one part completed, like the money sent to the organization with no record of what the money is for, the transaction is said to be "unbalanced" and a "dangling payment", as in, missing its bookkeeping counterpart).</value>
</data>
<data name="BalanceTransactions_ModalDialog_ButtonBalance" xml:space="preserve">
<value>Balance</value>
<comment>This is a verb in the imperative form - it's on a button.</comment>
</data>
<data name="BalanceTransactions_ModalDialog_ButtonOutboundInvoice" xml:space="preserve">
<value>Match invoice</value>
</data>
<data name="BalanceTransactions_ModalDialog_ButtonPayout" xml:space="preserve">
<value>Match</value>
<comment>This is a verb in the imperative form - it's on a button.</comment>
</data>
<data name="BalanceTransactions_ModalDialog_ButtonPayoutForeign" xml:space="preserve">
<value>Match</value>
</data>
<data name="BalanceTransactions_ModalDialog_ButtonPurchase" xml:space="preserve">
<value>Mark as Direct Purchase</value>
</data>
<data name="BalanceTransactions_ModalDialog_ButtonVatReport" xml:space="preserve">
<value>Close VAT report</value>
</data>
<data name="BalanceTransactions_ModalDialog_DescribeBalance" xml:space="preserve">
<value>Balance the difference against this account:</value>
</data>
<data name="BalanceTransactions_ModalDialog_DescribeOutboundInvoice" xml:space="preserve">
<value>Match the transaction to this outbound invoice:</value>
</data>
<data name="BalanceTransactions_ModalDialog_DescribePayout" xml:space="preserve">
<value>The transaction matches this payout:</value>
</data>
<data name="BalanceTransactions_ModalDialog_DescribePayoutForeign" xml:space="preserve">
<value>The transaction matches this foreign-currency payout:</value>
</data>
<data name="BalanceTransactions_ModalDialog_DescribePurchaseAmount" xml:space="preserve">
<value>Direct-debit purchase amount ({0})</value>
<comment>{0} is the currency</comment>
</data>
<data name="BalanceTransactions_ModalDialog_DescribePurchaseBudget" xml:space="preserve">
<value>Charge purchase to this budget</value>
</data>
<data name="BalanceTransactions_ModalDialog_DescribePurchaseDocUpload" xml:space="preserve">
<value>Upload receipt or other documentation</value>
</data>
<data name="BalanceTransactions_ModalDialog_DescribePurchaseTransaction" xml:space="preserve">
<value>Update transaction description</value>
</data>
<data name="BalanceTransactions_ModalDialog_DescribePurchaseVat" xml:space="preserve">
<value>VAT part of the amount</value>
</data>
<data name="BalanceTransactions_ModalDialog_DescribeVatReport" xml:space="preserve">
<value>This transaction is payment/return for this VAT report:</value>
</data>
<data name="BalanceTransactions_ModalDialog_DoYouWishTo" xml:space="preserve">
<value>Transaction is unbalanced by &lt;span id="spanTransactionUnbalancedBy"&gt;+FOO,BAR.QX&lt;/span&gt;. Do you wish to...</value>
</data>
<data name="BalanceTransactions_ModalDialog_RadioBalance" xml:space="preserve">
<value>Balance this transaction manually against an account?</value>
</data>
<data name="BalanceTransactions_ModalDialog_RadioOutboundInvoice" xml:space="preserve">
<value>Match this to an open outbound invoice?</value>
</data>
<data name="BalanceTransactions_ModalDialog_RadioOutboundInvoiceForeign" xml:space="preserve">
<value>Match this to an open outbound invoice in a nonstandard currency (5% forex tolerance)?</value>
</data>
<data name="BalanceTransactions_ModalDialog_RadioPayout" xml:space="preserve">
<value>Match the transaction difference to an open, unmatched payout?</value>
</data>
<data name="BalanceTransactions_ModalDialog_RadioPayoutForeign" xml:space="preserve">
<value>Map the transaction to a foreign-currency payout ({0}% amount tolerance)?</value>
</data>
<data name="BalanceTransactions_ModalDialog_RadioPurchase" xml:space="preserve">
<value>Mark this as a direct-from-account purchase?</value>
</data>
<data name="BalanceTransactions_ModalDialog_RadioVatReport" xml:space="preserve">
<value>Close a VAT report with this transaction?</value>
</data>
<data name="BalanceTransactions_ModalHeader" xml:space="preserve">
<value>Balancing/Matching Transaction #&lt;span id="spanModalTransactionId"&gt;67890&lt;/span&gt; From &lt;span id="spanModalTransactionDate"&gt;yyyy-mmm-dd&lt;/span&gt;</value>
<comment>The span text is replaced runtime.</comment>
</data>
<data name="BalanceTransactions_MostProbableMatch" xml:space="preserve">
<value>Most Probable Match</value>
<comment>This is the header of a match where the transaction description somehow matches the invoice reference.</comment>
</data>
<data name="BalanceTransactions_NoOpenPayouts" xml:space="preserve">
<value>(No open payouts)</value>
</data>
<data name="BalanceTransactions_NoSuitablePayouts" xml:space="preserve">
<value>(No suitable payouts to match)</value>
</data>
<data name="BalanceTransactions_NoUnbalancedTransactions" xml:space="preserve">
<value>There are no unbalanced transactions. Yay!</value>
<comment>Could also be translated to "everything is balanced" or similar. Try to not make it longer than the English text.</comment>
</data>
<data name="BalanceTransactions_OnePercentMatches" xml:space="preserve">
<value>Amount Within 1% Tolerance</value>
<comment>Header in selection list. Capitalize as customary for culture.</comment>
</data>
<data name="BalanceTransactions_OutboundInvoiceMatch" xml:space="preserve">
<value>Outbound Invoice #{0:N0} for {1}, due {2:yyyy-MMM-dd}: {3}</value>
<comment>Argument {0} is the invoice identity, {1} the customer name, {2} the due date and {3} the invoice-currencied amount (which can be different from the org's presentation currency)</comment>
</data>
<data name="BalanceTransactions_PageTitle" xml:space="preserve">
<value>Balance &amp; Match Transactions</value>
</data>
<data name="BalanceTransactions_PayoutMatch" xml:space="preserve">
<value>Payout #{0:N0}, {5} (expected {1:yyyy-MMM-dd}) for {2}: {3} {4:N2}</value>
<comment>0 is the payout Id, 1 is the date (do edit format if called for in culture), 2 is the recipient name, and 3 4 is the currency and amount, 5 is the specification (like "Expense Claim #4711")</comment>
</data>
<data name="BalanceTransactions_SelectPayout" xml:space="preserve">
<value>-- Select a Payout --</value>
</data>
<data name="BalanceTransactions_TenPercentMatches" xml:space="preserve">
<value>Amount Within 10% Tolerance</value>
<comment>Header in selection list. Capitalize as customary for culture.</comment>
</data>
<data name="BalanceTransactions_VatReportMatch" xml:space="preserve">
<value>VAT Report for {1:yyyy-MMM} surplus</value>
</data>
<data name="BitcoinHotwallet_Address" xml:space="preserve">
<value>Bitcoin Address</value>
</data>
<data name="BitcoinHotwallet_BalanceMicrocoins" xml:space="preserve">
<value>Balance microcoins</value>
</data>
<data name="BitcoinHotwallet_DerivationPath" xml:space="preserve">
<value>Derivation Path</value>
</data>
<data name="BitcoinHotWallet_Empty" xml:space="preserve">
<value>There are no funds in the hotwallet.</value>
</data>
<data name="BitcoinHotwallet_Header" xml:space="preserve">
<value>Hotwallet Breakdown</value>
<comment>"Breakdown" as in "zooming in to more details", not as in "ceasing to function".</comment>
</data>
<data name="BitcoinHotwallet_Info" xml:space="preserve">
<value>This shows a breakdown of the organization's bitcoin hotwallet addresses and balance. (Empty and previously-used addresses are not displayed.)</value>
</data>
<data name="BitcoinHotwallet_PageTitle" xml:space="preserve">
<value>Bitcoin Hotwallet</value>
</data>
<data name="BitcoinHotWallet_TransactionHash" xml:space="preserve">
<value>Transaction Hash</value>
</data>
<data name="BitcoinHotWallet_UnspentTransaction" xml:space="preserve">
<value>Unspent TxOut</value>
<comment>The local translation of a bitcoin UTXO (Unspent Transaction Output).</comment>
</data>
<data name="BitcoinHotwallet_ValueFiat" xml:space="preserve">
<value>Value {0}</value>
<comment>The {0} is the organization currency.</comment>
</data>
<data name="BudgetActual_ContentHeader" xml:space="preserve">
<value>Budget vs Actual</value>
</data>
<data name="BudgetActual_ExpectedYtd" xml:space="preserve">
<value>Expected YTD</value>
<comment>As in "expected actuals", as in when compared to budget. From the context, just "Expected" will also work.</comment>
</data>
<data name="BudgetActual_Info" xml:space="preserve">
<value>This page displays the budgeted breakdown compared to a breakdown of the actual outcome so far.</value>
</data>
<data name="BudgetActual_PageTitle" xml:space="preserve">
<value>Budget vs Actual</value>
<comment>Financial budget vs. Actual financial outcome</comment>
</data>
<data name="CloseLedgers_AnnualLoss" xml:space="preserve">
<value>Annual Loss</value>
</data>
<data name="CloseLedgers_AnnualProfit" xml:space="preserve">
<value>Annual Profit</value>
</data>
<data name="EndOfMonth_CheckHotWalletWithBlockchain" xml:space="preserve">
<value>Check Hotwallet Bitcoin Balance Against Blockchain</value>
<comment>This verifies the hotwallet data against master blockchain data, as per a blockchain explorer service or local crypto service node.</comment>
</data>
<data name="EndOfMonth_CheckLedgerAgainstHotWallet" xml:space="preserve">
<value>Resynchronize Ledger Bitcoin Balance Against Hotwallet</value>
<comment>This is the ledger balance of the hotwallet, which is supposed to say the hotwallet contains as much as it actually does.</comment>
</data>
<data name="EndOfMonth_CloseLedgersFor" xml:space="preserve">
<value>Close Financial Ledgers for Year {0}</value>
<comment>Parameter zero is the year as four digits. This EOM option is only presented once per year.</comment>
</data>
<data name="EndOfMonth_ConsolidateHotwallet" xml:space="preserve">
<value>Consolidate Bitcoin Hotwallet</value>
<comment>This rearranges the hotwallet for easy payouts going forward (collects all small amounts into even chunks)</comment>
</data>
<data name="EndOfMonth_ConvertBitcoinCoreToCash" xml:space="preserve">
<value>Convert the Bitcoin Core in Hotwallet to Bitcoin Cash</value>
<comment>This places an order on an exchange to convert BTC in the hotwallet to BCH</comment>
</data>
<data name="EndOfMonth_CreateVatReport" xml:space="preserve">
<value>Create {0}</value>
<comment>Parameter zero is the name of the VAT report as created localized in the logic layer</comment>
</data>
<data name="EndOfMonth_Dialog_LedgerBitcoinBalanceMismatch" xml:space="preserve">
<value>&lt;strong&gt;LEDGER BITCOIN BALANCE MISMATCH&lt;/strong&gt;&lt;br/&gt;&lt;br/&gt;The hotwallet has a balance of &lt;strong&gt;{0:N2}&lt;/strong&gt; microbitcoin, but the ledger says a different amount should be there: &lt;strong&gt;{1:N2}.&lt;/strong&gt; The hotwallet will always be in the right in a mismatch between these two, so the ledger has been adjusted to match the hotwallet.&lt;br/&gt;&lt;br/&gt;
This can happen after bitcoin splits (&amp;quot;forks&amp;quot;) or similar events, but if this happens repeatedly, month after month, and especially if money appears to be leaking from the hotwallet, there is cause for further investigation.
</value>
<comment>This is displayed after (!) the ledger bitcoin balance has been updated to match the hotwallet by means of a new transaction.</comment>
</data>
<data name="EndOfMonth_Error_Body_BankTransactionFileFormat" xml:space="preserve">
<value>The transaction file could not be processed. Is it the right file? For the right bank? Please try again.&lt;br/&gt;&lt;br/&gt;If the error persists, try getting a fresh transaction file.</value>
</data>
<data name="EndOfMonth_Error_Header_BankTransactionFile" xml:space="preserve">
<value>FILE COULD NOT BE IMPORTED</value>
</data>
<data name="EndOfMonth_FetchTransactionDataFor" xml:space="preserve">
<value>Autofetch Transaction Data for {0}</value>
<comment>Parameter zero is the account name as given by the user</comment>
</data>
<data name="EndOfMonth_Header_AnnualReports" xml:space="preserve">
<value>Annual Reports</value>
<comment>This is the header for closing of ledgers and generation of annual reports at the end-of-month routine</comment>
</data>
<data name="EndOfMonth_Header_Cryptocurrency" xml:space="preserve">
<value>Cryptocurrency</value>
<comment>This is the header for various bitcoin hotwallet / cold storage operations</comment>
</data>
<data name="EndOfMonth_Header_ExternalData" xml:space="preserve">
<value>External Account Data and Account Matching</value>
<comment>This is the header for uploading bank statements and resolving unmatched transactions at end-of-month.</comment>
</data>
<data name="EndOfMonth_Header_PayrollTaxes" xml:space="preserve">
<value>Payroll And Taxes</value>
<comment>This is the header for all tax reports and payroll processing for the end-of-month (start-of-next-month) routine.</comment>
</data>
<data name="EndOfMonth_Header_QuarterlyReports" xml:space="preserve">
<value>Quarterly Reports</value>
<comment>Presented in April, July, and October. Not in January (those are annual reports).</comment>
</data>
<data name="EndOfMonth_Info" xml:space="preserve">
<value>This is a checklist of things to do to close the previous month and begin the new one with respect to accounting.</value>
</data>
<data name="EndOfMonth_LedgerBitcoinBalanceTransactionDescription" xml:space="preserve">
<value>Ledger correction on hotwallet audit</value>
<comment>This is the description of a transaction that corrects the bitcoin balance in the ledger to equal that of the hotwallet.</comment>
</data>
<data name="EndOfMonth_MatchAccounts" xml:space="preserve">
<value>Resolve all dangling payments</value>
<comment>This means to match bank transactions with incoming/outgoing expected payments (invoices, expense reports, etc) where it couldn't be done automatically</comment>
</data>
<data name="EndOfMonth_PayrollInactive" xml:space="preserve">
<value>Payroll: No payroll defined</value>
<comment>This is shown as a disabled action item when there's no active payroll</comment>
</data>
<data name="EndOfMonth_SendReports" xml:space="preserve">
<value>Send Reports to Accountants, Shareholders, etc.</value>
<comment>This is the header for all items that send reports to external people at the end-of-month routine.</comment>
</data>
<data name="EndOfMonth_SkipBankStatementDialog" xml:space="preserve">
<value>&lt;strong&gt;SKIP BANK STATEMENT?&lt;/strong&gt;&lt;br/&gt;&lt;br/&gt;Bank statements are typically needed for audit verification of the internal records. The only valid reason to skip a month's statement is that the account wasn't opened yet, in which case you skip the months before the account was opened and no statements therefore exist.&lt;br/&gt;&lt;br/&gt;You won't be asked again to upload this particular statement if you skip it now.</value>
</data>
<data name="EndOfMonth_SkipDocumentDialogGeneric" xml:space="preserve">
<value>&lt;strong&gt;SKIP DOCUMENT UPLOAD?&lt;/strong&gt;&lt;br/&gt;&lt;br/&gt;This document is typically needed for operation records. The only valid reason to skip a document is that it doesn't exist because the operations weren't running yet, like when an operation started in June of a year won't have documents for January of that year.&lt;br/&gt;&lt;br/&gt;You won't be asked again to upload this document if you skip it now.</value>
</data>
<data name="EndOfMonth_Title" xml:space="preserve">
<value>End-of-Month Routine: {0:MMMM yyyy}</value>
<comment>Parameter zero is the month that's just ended</comment>
</data>
<data name="EndOfMonth_UploadBankStatementFor" xml:space="preserve">
<value>Upload Bank Statement ({1}) for {0} for {2}</value>
<comment>Parameter zero is the account name, parameter one the format (e.g. PDF), parameter two is the month (e.g. October 2018)</comment>
</data>
<data name="EndOfMonth_UploadTransactionDataFor" xml:space="preserve">
<value>Upload Transaction Data ({1}) for {0}</value>
<comment>Parameter zero is the account name, parameter one is the format (e.g. XML or CSV)</comment>
</data>
<data name="EndOfMonth_VerifyColdStorage" xml:space="preserve">
<value>Verify Cold Storage</value>
<comment>This verifies that the amounts supposed to be in cold storage are indeed in cold storage</comment>
</data>
<data name="EndOfMonth_Warning_Header_BankTransactionFile" xml:space="preserve">
<value>PROBLEM WITH TRANSACTION FILE</value>
</data>
<data name="InspectLedgers_AccountName" xml:space="preserve">
<value>Account name</value>
</data>
<data name="InspectLedgers_BalancedTransaction" xml:space="preserve">
<value>Balance is correct:</value>
</data>
<data name="InspectLedgers_CreateTransactionButton" xml:space="preserve">
<value>Create Transaction</value>
<comment>Text on button for executing create</comment>
</data>
<data name="InspectLedgers_CreateTransactionDateTime" xml:space="preserve">
<value>Date and time of transaction (UTC)</value>
</data>
<data name="InspectLedgers_CreateTransactionDescription" xml:space="preserve">
<value>Transaction Description</value>
</data>
<data name="InspectLedgers_CreateTransactionDialogHeader" xml:space="preserve">
<value>Creating New Transaction</value>
<comment>Header of dialog</comment>
</data>
<data name="InspectLedgers_CreateTransactionFirstAccount" xml:space="preserve">
<value>Account of first transaction row</value>
</data>
<data name="InspectLedgers_CreateTransactionFirstAmount" xml:space="preserve">
<value>Amount of first transaction row</value>
</data>
<data name="InspectLedgers_CreateTransactionSidebar" xml:space="preserve">
<value>Add new transaction</value>
<comment>Option in sidebar</comment>
</data>
<data name="InspectLedgers_Detail" xml:space="preserve">
<value>Description / Account</value>
<comment>As in, description of a transaction OR the full name of an account</comment>
</data>
<data name="InspectLedgers_EditingTransactionX" xml:space="preserve">
<value>Viewing/Editing Transaction #&lt;span id="spanModalTransactionId"&gt;67890&lt;/span&gt;</value>
<comment>The transaction id is replaced client-side on display</comment>
</data>
<data name="InspectLedgers_EmptyTransaction" xml:space="preserve">
<value>(No transaction data)</value>
</data>
<data name="InspectLedgers_FlaggingNotAvailable" xml:space="preserve">
<value>Flagging a transaction for closer inspection is not yet implemented. It is scheduled for one of the early Swarmops Red sprints, some time late 2015Q1.</value>
</data>
<data name="InspectLedgers_GeneralLedger" xml:space="preserve">
<value>General Ledger for</value>
<comment>This phrase is followed by dropdowns for year and month</comment>
</data>
<data name="InspectLedgers_HeaderAddTransactionRow" xml:space="preserve">
<value>Add rows to transaction</value>
<comment>(you can't really edit a transaction, just add more rows to it)</comment>
</data>
<data name="InspectLedgers_HeaderAutoTransactionTracking" xml:space="preserve">
<value>Autotransaction tracking details</value>
<comment>(this means the transaction is locked from editing)</comment>
</data>
<data name="InspectLedgers_Header_For" xml:space="preserve">
<value>for</value>
<comment>"inspect [accountdropdown] FOR [year] [month]"</comment>
</data>
<data name="InspectLedgers_Header_Hotwallet" xml:space="preserve">
<value>Inspect Bitcoin Cash Hotwallet For</value>
<comment>This is followed by a year and month dropdown</comment>
</data>
<data name="InspectLedgers_Header_Inspect" xml:space="preserve">
<value>Inspect</value>
<comment>"INSPECT [accountdropdown] for [year] [month]"</comment>
</data>
<data name="InspectLedgers_InboundBalance" xml:space="preserve">
<value>Inbound Balance</value>
</data>
<data name="InspectLedgers_InboundBalanceZero" xml:space="preserve">
<value>No Previous Balance</value>
</data>
<data name="InspectLedgers_Info" xml:space="preserve">
<value>This is the raw underlying Venetian bookkeeping ledgers for the organization's finances. You can study them here in detail for auditing purposes. &lt;span id="SpanInfoProfitLossAccount" style="display:none"&gt;&lt;strong&gt;You're currently watching a P&amp;L account, so signs are reversed - income is negative and expenses positive&lt;/strong&gt; due to how Venetian double bookkeeping works.&lt;/span&gt;</value>
</data>
<data name="InspectLedgers_InspectingTransactionX" xml:space="preserve">
<value>Inspecting Transaction #&lt;span id="spanModalTransactionId"&gt;12345&lt;/span&gt;</value>
<comment>The transaction id is replaced client-side on display</comment>
</data>
<data name="InspectLedgers_InspectNotAvailable" xml:space="preserve">
<value>Inspecting a single transaction is not yet implemented. It is scheduled for one of the early Swarmops Red sprints, late 2015Q1.</value>
</data>
<data name="InspectLedgers_LoggedByInitials" xml:space="preserve">
<value>Initials</value>
</data>
<data name="InspectLedgers_LoggedDate" xml:space="preserve">
<value>Logged</value>
</data>
<data name="InspectLedgers_NoTransactions" xml:space="preserve">
<value>There are no transactions in this account for the selected time period.</value>
</data>
<data name="InspectLedgers_OutboundBalance" xml:space="preserve">
<value>Outbound Balance</value>
</data>
<data name="InspectLedgers_OutboundBalanceZero" xml:space="preserve">
<value>Ending Balance</value>
</data>
<data name="InspectLedgers_OutboundBalanceZeroToDate" xml:space="preserve">
<value>Ending Balance (to date)</value>
<comment>Displayed if the end-balance date isn't reached yet</comment>
</data>
<data name="InspectLedgers_PageTitle" xml:space="preserve">
<value>Inspect Ledgers</value>
</data>
<data name="InspectLedgers_PleaseSelectAccount" xml:space="preserve">
<value>(Please select an account.)</value>
<comment>Displayed initially and when no valid account selected</comment>
</data>
<data name="InspectLedgers_TransactionId" xml:space="preserve">
<value>Tx#</value>
<comment>Keep VERY short.</comment>
</data>
<data name="InspectLedgers_TxDetail_AttestedByX" xml:space="preserve">
<value>Attested by {0} on {1:yyyy-MMM-dd}</value>
</data>
<data name="InspectLedgers_TxDetail_CombinedWith" xml:space="preserve">
<value>combined with</value>
<comment>Inserted between transaction causes.</comment>
</data>
<data name="InspectLedgers_TxDetail_DescriptionWithheld" xml:space="preserve">
<value>(detailed description withheld)</value>
</data>
<data name="InspectLedgers_TxDetail_ErrorAddRowNoAccount" xml:space="preserve">
<value>Please select an account in order to add a row to this transaction.</value>
</data>
<data name="InspectLedgers_TxDetail_InvoiceX" xml:space="preserve">
<value>&lt;strong&gt;Inbound Invoice #{0:N0}&lt;/strong&gt; from {1}:</value>
<comment>the {1} is the supplier name</comment>
</data>
<data name="InspectLedgers_TxDetail_PaidOutBy" xml:space="preserve">
<value>Executed by {0}.</value>
<comment>As in "payout executed by": who actually paid the money?</comment>
</data>
<data name="InspectLedgers_TxDetail_SalaryDetail" xml:space="preserve">
<value>Base salary {0} {1:N2}, gross adjustments {2:+N2;-N2;none}, gross salary {3:N2}, deducted tax {4:N2}, net adjustments {5:+N2;-N2;none}, payout {6:N2}.</value>
<comment>The "none"s in the format strings need to be translated.</comment>
</data>
<data name="InspectLedgers_TxDetail_ThisIsPayoutX" xml:space="preserve">
<value>This is &lt;strong&gt;Payout #{0:N0}.&lt;/strong&gt; It's a payout for</value>
</data>
<data name="InspectLedgers_TxDetail_ValidatedByX" xml:space="preserve">
<value>Document validation by {0} on {1:yyyy-MMM-dd}</value>
<comment>"Document" refers to receipts, invoices, etc.</comment>
</data>
<data name="InspectLedgers_TxInfo_CloseVatReport" xml:space="preserve">
<value>This transaction closes the VAT report for {0}.</value>
<comment>{0} will be a time period, like "Jan 2017".</comment>
</data>
<data name="InspectLedgers_TxInfo_OpenVatReport" xml:space="preserve">
<value>This transaction opens the VAT report for {0}.</value>
<comment>{0} will be a time period, like "Jan 2017".</comment>
</data>
<data name="InspectLedgers_TxInfo_PaymentInvoice" xml:space="preserve">
<value>This transaction receives payment for Outbound Invoice #{0:N0}.</value>
</data>
<data name="InspectLedgers_TxInfo_PayoutGeneric" xml:space="preserve">
<value>This transaction pays {0}.</value>
</data>
<data name="InspectLedgers_TxInfo_PayoutInvoice" xml:space="preserve">
<value>This transaction pays Inbound Invoice #{0:N0} from {1}.</value>
</data>
<data name="InspectLedgers_UnbalancedTransaction" xml:space="preserve">
<value>Transaction is &lt;span class="spanAnnoyingBlink"&gt;UNBALANCED:&lt;/span&gt; missing amount</value>
</data>
<data name="ProfitLossStatement_AccountName" xml:space="preserve">
<value>Account</value>
</data>
<data name="ProfitLossStatement_ContentHeader" xml:space="preserve">
<value>P&amp;L for {0} for</value>
<comment>The {0} is the organization name. The year number follows this string.</comment>
</data>
<data name="ProfitLossStatement_DownloadFileName" xml:space="preserve">
<value>ProfitLoss</value>
<comment>Must ONLY contain A-Z, a-z characters - nothing accented!</comment>
</data>
<data name="ProfitLossStatement_Info" xml:space="preserve">
<value>The P&amp;L is an overview of income and expenditures, which are grouped by budgets or cost/income type. The sum of all income and expenditure is the yearly result. You may also want to look at the &lt;a href="BalanceSheet"&gt;balance sheet&lt;/a&gt; which is the overview of assets and debts.</value>
</data>
<data name="ProfitLossStatement_LastYear" xml:space="preserve">
<value>Last Year</value>
</data>
<data name="ProfitLossStatement_PageTitle" xml:space="preserve">
<value>Profit &amp; Loss Statement</value>
</data>
<data name="ProfitLossStatement_Results" xml:space="preserve">
<value>Results</value>
<comment>Footer on P&amp;L statement</comment>
</data>
<data name="ProfitLossStatement_Ytd" xml:space="preserve">
<value>YTD</value>
<comment>Year To Date</comment>
</data>
<data name="ResyncExternalAccount_Info" xml:space="preserve">
<value>If your bookkeeping in Swarmops has gotten out of sync with your bank records for whatever technical or human reason, you can resynchronize them here by uploading a master file that covers the time frame you need to resync.&lt;br/&gt;&lt;br/&gt;&lt;strong&gt;Warning:&lt;/strong&gt; this is a time-consuming process that may do a &lt;em&gt;lot&lt;/em&gt; of changes to your bookkeeping. Do not use unless you have discovered a mismatch in the records vs. your bank.&lt;br/&gt;&lt;br/&gt;(You will get a chance to review proposed changes before they are committed to your financial records.)</value>
</data>
<data name="ResyncExternalAccount_PageTitle" xml:space="preserve">
<value>Resynchronize Bank Account</value>
</data>
<data name="SetRootBudgets_BudgetOwnerHeader" xml:space="preserve">
<value>Budget, Owner</value>
<comment>Displayed above editables</comment>
</data>
<data name="SetRootBudgets_Info" xml:space="preserve">
<value>This is where the root budgets are set for each budget year. After these are set, each budget owner suballocates funds within their respective budget trees.</value>
</data>
<data name="SetRootBudgets_PageHeader" xml:space="preserve">
<value>Root Budgets For {0}</value>
<comment>The {0} is replaced with the organization's name.</comment>
</data>
<data name="SetRootBudgets_PageTitle" xml:space="preserve">
<value>Set Root Level Budgets</value>
<comment>Displayed above main content</comment>
</data>
<data name="SetRootBudgets_SetNewBudgets" xml:space="preserve">
<value>Set New Budgets</value>
<comment>Text on submit button</comment>
</data>
<data name="TaxForms_Payroll_AdditiveTax" xml:space="preserve">
<value>Additive Tax</value>
<comment>If applicable, translate to local legal tax term</comment>
</data>
<data name="TaxForms_Payroll_DeductedTax" xml:space="preserve">
<value>Deducted Tax</value>
<comment>If applicable, translate to local legal tax term</comment>
</data>
<data name="TaxForms_Payroll_GrossPay" xml:space="preserve">
<value>Gross Paycheck</value>
</data>
<data name="TaxForms_Payroll_Info" xml:space="preserve">
<value>View cheat sheets (completed tax forms) for the organization payroll, which are easy for you to copy to your actual tax forms, or possibly even print as is. Performance and actual forms vary by country and sometimes depend on third-party code and plugins.</value>
</data>
<data name="TaxForms_Payroll_PageTitle" xml:space="preserve">
<value>Payroll Tax Forms</value>
</data>
<data name="TaxForms_Payroll_TaxFormsMonthlyHeader" xml:space="preserve">
<value>Monthly Tax Forms For</value>
<comment>The {0} is the organization name. A country selector follows (imagine a "France" tacked on to the end).</comment>
</data>
<data name="TaxForms_Payroll_TotalCost" xml:space="preserve">
<value>Total Cost</value>
</data>
<data name="TaxForms_Payroll_TotalTax" xml:space="preserve">
<value>Total Tax</value>
</data>
<data name="UploadBankFiles_AccountAutomationProfile" xml:space="preserve">
<value>Automation Profile</value>
<comment>This is where the bank name, country, and currency appears.</comment>
</data>
<data name="UploadBankFiles_AccountStatement" xml:space="preserve">
<value>Account Statement</value>
</data>
<data name="UploadBankFiles_BankAccount" xml:space="preserve">
<value>Bank Account</value>
</data>
<data name="UploadBankFiles_BankScreenshot" xml:space="preserve">
<value>Bank Screenshot</value>
<comment>Displayed as header above modally zoomed screenshot</comment>
</data>
<data name="UploadBankFiles_DownloadDataSince" xml:space="preserve">
<value>&lt;/p&gt;&lt;p&gt;(The most recent data in Swarmops in &lt;em&gt;{0}&lt;/em&gt; is from {1:yyyy-MMM-dd}. You should download bank data from at least &lt;strong&gt;{2:yyyy-MMM-dd}.&lt;/strong&gt;)</value>
<comment>Displayed to help user determine scope of bank download</comment>
</data>
<data name="UploadBankFiles_DownloadDataSince_Paypal" xml:space="preserve">
<value>&lt;/p&gt;&lt;p&gt;(Paypal will tell you the time of the last transaction download. Download all transactions from that point in time, adding some three days of overlap.)</value>
<comment>Displayed instead of date of last transaction in the case of Paypal.</comment>
</data>
<data name="UploadBankFiles_DownloadInstructions" xml:space="preserve">
<value>Bank Download Instructions</value>
<comment>Header above instructions for generation of the bank file type selected.</comment>
</data>
<data name="UploadBankFiles_ErrorBalance" xml:space="preserve">
<value>&lt;p&gt;The file contained {0:N0} transactions. &lt;strong&gt;{1:N0} transactions&lt;/strong&gt; have been successfully imported into the &lt;em&gt;{2}&lt;/em&gt; bookkeeping account. ({3:N0} transactions were duplicates.)&lt;/p&gt;&lt;p&gt;&lt;strong&gt;However, the bank balance does not match the records in Swarmops.&lt;/strong&gt; This is usually due to missing transactions. Please upload a transaction list with a larger time span to make sure that Swarmops sees all transactions.&lt;/p&gt;&lt;p&gt;Swarmops's bookkeeping account is currently &lt;strong&gt;not in sync&lt;/strong&gt; with that of the bank.&lt;/p&gt;</value>
<comment>Displayed when import successful, but end balance out of sync. Assumes plural along all pasted numbers.</comment>
</data>
<data name="UploadBankFiles_ErrorInterpretation" xml:space="preserve">
<value>&lt;h3&gt;The bank file could not be imported.&lt;/h3&gt;&lt;p&gt;This has one of three reasons: you missed some detail in the download instructions, the bank has changed its format, or you accidentally uploaded the wrong file entirely (like a photo from your last party instead of the transactions list). No transactions were imported at all. &lt;strong&gt;Please retry.&lt;/strong&gt;</value>
</data>
<data name="UploadBankFiles_Error_NoAutomationProfiles" xml:space="preserve">
<value>There are no asset accounts set up for automation, so no accounts support data upload at this time. Returning to Dashboard.</value>
</data>
<data name="UploadBankFiles_ExpectedFile" xml:space="preserve">
<value>Expected File</value>
<comment>The name of the expected file for uploading.</comment>
</data>
<data name="UploadBankFiles_FileImportedHeader" xml:space="preserve">
<value>File Successfully Imported</value>
<comment>Displayed as header after successful processing</comment>
</data>
<data name="UploadBankFiles_FileImportedHeader_ErrorBalance" xml:space="preserve">
<value>File Imported, But Data Out Of Sync</value>
<comment>Displayed as header after a good processing that ended in sync failure</comment>
</data>
<data name="UploadBankFiles_FileType" xml:space="preserve">
<value>File Type</value>
<comment>can be Account Statement or Payments File</comment>
</data>
<data name="UploadBankFiles_ImportError" xml:space="preserve">
<value>Error on importing file</value>
<comment>Displayed as header on import failure</comment>
</data>
<data name="UploadBankFiles_ImportResults" xml:space="preserve">
<value>&lt;p&gt;The file contained {0:N0} transactions. &lt;strong&gt;{1:N0} transactions&lt;/strong&gt; have been successfully imported into the &lt;em&gt;{2}&lt;/em&gt; bookkeeping account. ({3:N0} transactions were duplicates.)&lt;/p&gt;&lt;p&gt;After import, the account balance in Swarmops matches that of the bank.&lt;/p&gt;</value>
<comment>Displayed on successful import. Assumes plural among all pasted numbers.</comment>
</data>
<data name="UploadBankFiles_Info" xml:space="preserve">
<value>Here, you can upload files from your bank or payment provider into your organization's bookkeeping. Examples include account history and payments received.</value>
<comment>Displayed in sidebar on page.</comment>
</data>
<data name="UploadBankFiles_Instructions" xml:space="preserve">
<value>Instructions</value>
</data>
<data name="UploadBankFiles_PageTitle" xml:space="preserve">
<value>Upload Bank Files</value>
<comment>Displayed above main content.</comment>
</data>
<data name="UploadBankFiles_PaymentAllDuplicates" xml:space="preserve">
<value>However, they were all duplicates of payment information that was previously uploaded. No new payment information has been imported to Swarmops.</value>
</data>
<data name="UploadBankFiles_PaymentCount" xml:space="preserve">
<value>no payments|one payment|{0} payments</value>
<comment>none|one|many</comment>
</data>
<data name="UploadBankFiles_PaymentFileUploadedHeader" xml:space="preserve">
<value>Payment File Uploaded</value>
</data>
<data name="UploadBankFiles_PaymentGroupCount" xml:space="preserve">
<value>no payment groups|one payment group|{0} payment groups</value>
<comment>none|one|many</comment>
</data>
<data name="UploadBankFiles_PaymentsFile" xml:space="preserve">
<value>Payments File</value>
</data>
<data name="UploadBankFiles_PaymentSummary1" xml:space="preserve">
<value>The payment file contained {0}.</value>
</data>
<data name="UploadBankFiles_PaymentSummary2" xml:space="preserve">
<value>&lt;strong&gt;{0} {1:N2}&lt;/strong&gt; in payments were imported, distributed over {2} across {3}.</value>
<comment>like EUR 2,102.00 in 3 payments across 2 groups </comment>
</data>
<data name="UploadBankFiles_PaymentSummaryDuplicates" xml:space="preserve">
<value>There was also some duplicate information ({0} across {1}).</value>
</data>
<data name="UploadBankFiles_Processing" xml:space="preserve">
<value>Processing File...</value>
</data>
<data name="UploadBankFiles_ProcessingComplete" xml:space="preserve">
<value>Processing Complete</value>
</data>
<data name="UploadBankFiles_ResultsBad" xml:space="preserve">
<value>&lt;p&gt;&lt;br/&gt;&lt;strong&gt;The file could not be read as an input file to this bank.&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;There are several reasons this could happen: the file may be corrupt, the bank may have silently changed its file format, or you uploaded the wrong file entirely. Please try again.&lt;/p&gt;</value>
<comment>Displayed when the input file can't be parsed, before import attempt.</comment>
</data>
<data name="UploadBankFiles_ResultsGood" xml:space="preserve">
<value>&lt;p&gt;The file has been &lt;strong&gt;successfully imported.&lt;/strong&gt; {0:N0} new transactions imported; {1:N0} discarded as duplicates of what was already in Swarmops. The account balance in Swarmops matches that of the bank.&lt;/p&gt;&lt;p&gt;The file contained transactions from {2:yyyy-MMM-dd} to {3:yyyy-MMM-dd}.&lt;/p&gt;</value>
<comment>Zero is new transaction count, one is duplicate transaction count, two and three are lowest and highest dates found in file. Pay attention to date format and adjust to culture.</comment>
</data>
<data name="UploadBankFiles_ResultsInitialBalanceSet" xml:space="preserve">
<value>As this was the first upload to this automated account, the initial balance of &lt;strong&gt;{0} {1:N2}&lt;/strong&gt; going into the year {2} has been detected and set</value>
<comment>{1} {2:N2} is the currency and amount, like USD 2,151.00.</comment>
</data>
<data name="UploadBankFiles_ResultsInitialBalanceSetForeignCurrency" xml:space="preserve">
<value>(which was accounted for with &lt;strong&gt;{0} {1:N2}&lt;/strong&gt; in the ledger operating currency)</value>
<comment>{0} {1:N2} is a currency and amount, which is how an initial bank balance in a foreign currency was entered into the ledgers after converting to the organization's accounting currency</comment>
</data>
<data name="UploadBankFiles_ResultsPayments" xml:space="preserve">
<value>&lt;br/&gt;&lt;p&gt;The payments file was &lt;strong&gt;successfully imported.&lt;/strong&gt; {1:N0} payment(s) in {0:N0} group(s), totalling {3} {2:N2}, were imported.&lt;/p&gt;</value>
<comment>Arguments 0-3 in order: 0 PaymentGroupCount, 1 PaymentCount, 2 PaymentAmountTotal, 3 Currency</comment>
</data>
<data name="UploadBankFiles_ResultsPaymentsWithDupes" xml:space="preserve">
<value>&lt;br/&gt;&lt;p&gt;The payments file was &lt;strong&gt;successfully imported.&lt;/strong&gt; {1:N0} payment(s) in {0:N0} group(s), totalling {3} {2:N2}, were imported.&lt;/p&gt;&lt;p&gt;(There were also {5:N0} duplicate payment(s) in {4:N0} group(s).)&lt;/p&gt;</value>
<comment>Arguments 0-5 in order: 0 PaymentGroupCount, 1 PaymentCount, 2 PaymentAmountTotal, 3 Currency, 4 DuplicatePaymentGroupCount, 5 DuplicatePaymentCount</comment>
</data>
<data name="UploadBankFiles_ResultsQuestionable" xml:space="preserve">
<value>&lt;p&gt;The file was imported, but the &lt;strong&gt;resulting account balance mismatches.&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;After importing {0:N0} transactions (and discarding {1:N0} duplicates), the entire file has been processed. However, the resulting account balance in Swarmops is not the same as that of the bank statement; there is a difference of {3} {2:N2}.&lt;/p&gt;
&lt;p&gt;Please try uploading a fresh account statement. If that still produces a mismatch, you may need to try &lt;a href="/Pages/v5/Ledgers/ResyncExternalAccount.aspx"&gt;resynchronizing&lt;/a&gt; the bank account with a comprehensive account statement file.&lt;/p&gt;</value>
<comment>Displayed on successful import, but the resulting balance is off compared to the account statement file that was just uploaded. 2 is the diff, 3 is the currency.</comment>
</data>
<data name="UploadBankFiles_SelectAccount" xml:space="preserve">
<value>Select Bookkeeping Account</value>
<comment>Select prompt for the financial account in the organization's bookkeeping.</comment>
</data>
<data name="UploadBankFiles_SelectBankAndAccount" xml:space="preserve">
<value>Select File Type And Account For Upload</value>
</data>
<data name="UploadBankFiles_SelectBankFileType" xml:space="preserve">
<value>Select Bank File Type</value>
<comment>Header above several bank logos, prompting a selection of bank.</comment>
</data>
<data name="UploadBankFiles_UploadAnother" xml:space="preserve">
<value>Upload another bank file?</value>
<comment>Displayed as header after uploading one file</comment>
</data>
<data name="UploadBankFiles_UploadBankFile" xml:space="preserve">
<value>Upload bank file</value>
<comment>Displayed as header above download instructions / upload form</comment>
</data>
<data name="ViewOutstandingAccounts_FooterDifference" xml:space="preserve">
<value>Difference</value>
</data>
<data name="ViewOutstandingAccounts_FooterLedgerBalance" xml:space="preserve">
<value>Ledger Balance</value>
</data>
<data name="ViewOutstandingAccounts_FooterTotal" xml:space="preserve">
<value>Total</value>
</data>
<data name="ViewOutstandingAccounts_GridHeaderAction" xml:space="preserve">
<value>Action</value>
<comment>keep short</comment>
</data>
<data name="ViewOutstandingAccounts_GridHeaderAmount" xml:space="preserve">
<value>Amount</value>
<comment>keep short</comment>
</data>
<data name="ViewOutstandingAccounts_GridHeaderDescription" xml:space="preserve">
<value>Description</value>
</data>
<data name="ViewOutstandingAccounts_GridHeaderExpectedCloseDate" xml:space="preserve">
<value>Exp Close</value>
<comment>keep short</comment>
</data>
<data name="ViewOutstandingAccounts_GridHeaderId" xml:space="preserve">
<value>ID#</value>
<comment>keep short</comment>
</data>
<data name="ViewOutstandingAccounts_GridHeaderOpenedDate" xml:space="preserve">
<value>Opened Date</value>
<comment>keep short</comment>
</data>
<data name="ViewOutstandingAccounts_GridHeaderRecipient" xml:space="preserve">
<value>Recipient</value>
</data>
<data name="ViewOutstandingAccounts_Header" xml:space="preserve">
<value>List Unsettled</value>
</data>
<data name="ViewOutstandingAccounts_Info" xml:space="preserve">
<value>This page lets you verify the outstanding and unsettled accounts (expenses, invoices, cash advances, etc.) at the current point in time or at the time of closing of any previous ledger.</value>
</data>
<data name="ViewOutstandingAccounts_PageTitle" xml:space="preserve">
<value>List Unsettled Accounts</value>
</data>
<data name="ViewVatReports_EmptyReport" xml:space="preserve">
<value>-- nothing to report --</value>
<comment>This is displayed when there are no items at all in a VAT report.</comment>
</data>
<data name="ViewVatReports_Footer_Total" xml:space="preserve">
<value>Report Totals</value>
</data>
<data name="ViewVatReports_Header_DateTime" xml:space="preserve">
<value>Date/Time</value>
<comment>Timestamp of transaction</comment>
</data>
<data name="ViewVatReports_Header_Description" xml:space="preserve">
<value>Description</value>
<comment>Description of transaction</comment>
</data>
<data name="ViewVatReports_Header_Dox" xml:space="preserve">
<value>Docs</value>
<comment>This is above the "view documents" icon</comment>
</data>
<data name="ViewVatReports_Header_Inbound" xml:space="preserve">
<value>Inbound VAT</value>
</data>
<data name="ViewVatReports_Header_NoReports" xml:space="preserve">
<value>No VAT reports for this organization</value>
</data>
<data name="ViewVatReports_Header_Outbound" xml:space="preserve">
<value>Outbound VAT</value>
</data>
<data name="ViewVatReports_Header_Turnover" xml:space="preserve">
<value>Turnover</value>
</data>
<data name="ViewVatReports_Info" xml:space="preserve">
<value>You're viewing a filed VAT report. The inbound and outbound VAT, as well as total turnover, have been recorded for the report period. This report is ready to be transmitted to tax authorities.</value>
</data>
<data name="ViewVatReports_NoReports" xml:space="preserve">
<value>There are no VAT reports to display. This is probably due to the fact that a full VAT reporting period has not elapsed yet, so it has not been possible to create a report yet.</value>
</data>
<data name="ViewVatReports_PageTitle" xml:space="preserve">
<value>VAT Reports</value>
<comment>VAT is short for Value Added Tax; it has completely different names in different EU countries (moms, Umsatzsteuer, etc.)</comment>
</data>
<data name="ViewVatReports_ReportTotals" xml:space="preserve">
<value>Totals for this report</value>
<comment>Displayed as description of footer</comment>
</data>
<data name="ViewVatReports_Title_View" xml:space="preserve">
<value>View</value>
<comment>This is the word or words before the name of the displayed VAT report.</comment>
</data>
</root>